Topic: test & qa

Test & QA
Test and QA Stories

Once a testable requirement or acceptance criteria has been “created,” there is a tendency to assume that the task can be considered completed. Since 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?

Discovering performance issues in early builds allows more time to correct the design. By including critical performance-related features and elements earlier, we can take advantage of the incremental nature of the development process to avoid creating engineering in potential performance issues.

A tool architecture is simply a picture of all your development, testing, and deployment tools and how they fit together. Creating a "current state" diagram and then looking forward and creating a "future state" diagram helps you understand where tool integrations would be beneficial.

Google is one of many tech companies called out for a lack of diversity in their workforce. To change their company mindset, Google is endeavoring to help employees change their unconscious biases. Pamela Rentz highlights what others can learn from Google's workplace bias training.

Enterprise software has long existed and grown with changes in technology. During a shift in focus to mobile computing, mobile app development, and enterprises working to embrace the cloud, it would not be unfair to say that enterprise software was briefly sidelined―but it's making a resurgence.