Topic: test & qa
In our drive for better quality and productivity, we are coming close to realizing full continuous application lifecycle management. Continuous testing is emerging as a best practice that focuses on developing testing procedures, primarily automated, to meet the need for fast application testing.
In this STARWEST 2014 keynote, Ben Simo shares his experience with HealthCare.gov, the issues he found, and lessons testers can learn from the website's failures. He digs into everything he had to do to discover the many flaws of the government website.
In this STARWEST 2014 keynote, Julie Gardiner goes into how to make the business case for including test professionals in software evaluation in order to add their unique focus on software quality. She gives advice on how to talk to managers and produce better software.
Often, what automation “does” directly relates to the bottom line. This has loosely been interpreted as the misconception that the more automation you have, the fewer people you will need on your payroll. Melissa Tondi focuses on what automation does not do to give a more accurate idea.
Once a testable requirement or acceptance criteria have been “created,” there is a tendency to assume that the task can be considered completed. Because that may or may not be true, it is better to continue to pay attention to testability. Here are four ways to maintain testable requirements.
Paco Hope, principal consultant for Cigital, presented the last keynote of STARWEST 2014: “Softwarts: Security Testing for Muggles.” He exposed some testing fallacies, gave four principles for security testing, and detailed some charms every good testing wizard should have in his spell book.
A smart meter records consumption of electric energy and communicates that information daily to the utility company for monitoring and billing. Given the architecture, about half of the device maintenance effort is testing. Though the process is unique, the same basic testing imperatives apply.
If we look at keywords essential to information processing, searchability and discoverability are critical. Any piece of information an organization has access to needs to become searchable and discoverable to the relevant end-users when they need it. This is presenting new business opportunities.
When it comes to ISO 29119, the new international standard for software testing, there is a great deal of secrecy around it. Matt Heusser has the papers published so far, so he explains and shares his thoughts about Section 5—a document that is basically a collection of documents and definitions.
Automation technology is becoming more prevalent, and while it brings convenience, it also introduces some moral quandaries. Someone has to decide what the devices will do when things go wrong. What are the ethical responsibilities of software developers and testers working on these projects?