Recently, I’ve spent time talking with our customers and prospects in the health care space about their efforts to become ICD-10 compliant. The common refrain from all of them has been, “brute force isn’t going to work at this late juncture.” There’s just not enough time or people on their IT teams to do all of the testing that’s necessary between now and October 1, 2014.
Mark Lott, president of Lott QA Group, will join us to discuss how healthcare organizations can confidently deploy system upgrades to satisfy current and upcoming technology initiatives. If you’re just now starting to review and assess the systems that will be impacted, or starting to plan the upgrade and testing effort needs to become ICD-10 compliant, you won’t want to miss this webinar.
We understand that you need to prioritize testing efforts to get the most bang for your testing buck. To help you realize that goal, Mark will:
Explain how to more effectively test new and upgraded systems and gain better insight into revenue risk
Discuss the key objectives for any successful testing initiative
Outline the reports and metrics your team should focus on
As part of this discussion, Seapine will demonstrate how TestTrack can help manage all ICD-10 integration testing and development artifacts. TestTrack is Seapine’s suite of tools for managing application development phases and artifacts.
The WEDI conference takes place in North Harbor, Maryland, November 18-21.
In our recently completed 2013 State of Medical Device Development Survey we asked medical device professionals, “What are the top three pieces of information or insights you wish you had better visibility into during the design control phase?” The most common response? Risk controls!
If you look at the responses to another question we asked about how teams are managing their risk artifacts, you won’t be surprised that folks are struggling with visibility into those artifacts. Almost 90% of teams are using documents to manage risk identification, analysis, and mitigation.
Surround SCM 2013.2 was recently released and we have documentation updates to share with you. Check out the following help topics to learn more about new features and enhancements added in this release.
Surround SCM 2013.2 introduces trigger support for code reviews and files in reviews. This enhancement allows you to edit email templates used in the default code review workflow, add new triggers to automate additional code review actions, and create email notifications to be automatically notified of changes to files in your code reviews as they move through the review process.
Editing email templates for the default code review workflow
The default code review workflow is controlled by 4 built-in triggers that email reviewers when reviews start or are overdue and email authors when reviews need attention or are approved. Users with permission to manage triggers can edit the email templates used with these triggers to specify the information included in the email sent to users.
Thanks for everyone that participated in the “Beyond FDA Compliance Webinar: 5 Hidden Benefits of Your Traceability Matrix” webinar. The webinar recording is now available if you weren’t able to attend or if you would like to watch it again. Transcript from the webinar Q & A follows.
Many testing teams rely solely on scripted testing, both manual and automated, to decrease the risk of defects in the product release. The problem is, scripted testing is not meant to identify error conditions in scenarios that significantly deviate from the design or requirements. To find these hidden or divergent risks, you need to go off script, and that’s where adding exploratory testing can help.
It’s almost impossible to plan tests that cover every variation in data, configuration, interaction, sequence, timing, and so on. Scripted tests are designed to ensure that the application meets the requirements (using new-feature test cases) and to mitigate the risk of new features breaking existing functionality (via regression test cases).
Experienced testers can anticipate issues that might occur, but it may too costly or time-consuming to write a test case for every scenario that comes to mind.
In her book Explore It! Reduce Risk and Increase Confidence with Exploratory Testing, Elisabeth Hendrickson says the best test strategy answers two core questions:
Does the software behave as intended under the conditions it’s supposed to be able to handle?
Are there any other risks?
Scripted testing can answer the first question, but to find those potentially critical “other risks,” you need to explore. Continue reading…
The Seapine Technical Writing team relies heavily on Surround SCM’s shelves. Shelves are containers stored on the Surround SCM Server where you can store new and modified files from a working directory before adding or checking them in to Surround SCM. We use shelves to share documentation files for peer review.
For example, when I finish writing new topics or editing existing topics, I shelve the files and share the shelf with another team member. They can unshelve the files to copy them to their working directory, review them and add any changes, and then create a new shelf to add the changed files to. I unshelve the changed files to my working directory, accept the changes or make additional changes in the files, and then delete both shelves. I can then check in or add files to Surround. It is an easy process that helps us ensure that all files go through review before they are checked in or published. Continue reading…