White Papers & Downloads

Insights and analysis from thought leaders in testing/QA, agile development and testing, requirements, mobile testing, DevOps, and more. These white papers from SQE Training's expert instructors bring you insight into best practices, career strategies and guidance, analysis of common software development processes, and more.

The results of TechWell’s second annual survey show the role of tester continues to evolve and adapt thanks to the increasing influence of automation, DevOps, and agile. Responsibilities and skill sets are still expanding to include more technical skills and domain knowledge. And, most importantly, the role of tester seems to be holding strong for the foreseeable future. 

The inaugural TechWell State of the Testing Profession survey sets a baseline measurement of attitudes about the testing profession, with an eye toward repeating the survey annually to track trends and changes. The survey not only collected data on the current state of testing, but it also gathered feedback on evolving tester roles and responsibilities, new skills and knowledge requirements, and opinions on the outlook for the testing profession.

The data collected from 529 software professionals, including testers, managers, developers, analysts, and consultants, suggest that the testing profession isn’t going away; it’s just going to be different.

Business analysis is often seen as a technical skill. The business analyst is called upon to build process and data models, writes precise requirements, estimate the effort involved, and more. But a business analyst has another set of responsibilities—to uncover what it is that stakeholders actually need.

Originators of the Volere requirements process, template, checklists and techniques, James Robertson and Suzanne Robertson discuss why the most successful business analysts have a uniqe combintation of hard and soft skills in this paper.

A common problem contributing to software development project failure is a failure of requirements. Is it possible that the user story directly contributes to this requirements failure?

In this paper, SQE Training instructors James Robertson and Suzanne Robertson address why user stories are often poor in the requirements arena. They dissect the anatomy of a user story and offer tips on how to write stories that address value to the organization, not just solutions.

There are numerous tools available for designing test cases from the requirements. They all use just one of two approaches: combinatorics techniques (i.e., pair-wise testing) or model-based testing. Within model-based testing there is a refined approach which sensitizes the path to ensure that defects are propagated to an observable point—requirements-based testing.

In this paper, SQE Training instructor Richard Bender defines what requirements-based testing is and the comparison criteria used to determine which approach is the most effective and most efficient. Each of the approaches are then measured against the criteria. Bender has more than forty-five years experience in software with a primary focus on quality assurance and testing. Bender RBT Inc. is the recognized authority on cause-effect modeling and test generation.

The IT industry continues to change at lightning speed. This presents significant challenges for all of the roles involved in delivering high-quality software—and the testing role is no exception. Keeping pace with changing technology can be a full-time job in itself, but in addition there is the critical work of verifying and validating software systems and applications and delivering high-quality solutions to our customers.

In this paper we explore the challenges that we face as testers in keeping up with the technology revolution and discuss a few strategies to ensure that we stay current with our changing and challenging world. These tactics assure that our expertise remains relevant, not just in our present jobs or roles, but for the future as well.