This learning track covers a wide range of topics including the differences between agile and traditional software testing approaches, agile testing strategies and techniques, and test automation. You will gain an understanding of the tightly-coupled nature of agile testing and development throughout the lifecycle of product development, and the necessary degree of collaboration among the business, developers, and testers to produce high-value, high-quality software. Our focus is primarily on the mindset and role of an agile tester, while also covering agile testing techniques and processes - in an effort to “agilize” testing so that you can best collaborate on an agile development cadence.
Primary Audience: Individuals with a passion for software quality and a desire to learn testing techniques and/or test automation, Test Managers with an interest in learning or improving automation skills and Developers with an interest in automation beyond unit testing.
Relevant Roles: Testers, Test Engineers, Test Managers, Analysts, and Developers with an interest in testing.
In agile development, both verification and validation happen as close to simultaneously as possible. Largely, this is due to the necessity to keep refining and updating the user stories, requiring small V&V loops for continuous feedback.
This resource is more like an online book than an article, taking you step-by-step in the journey to implementing continuous testing. It covers the management of source code, environments and infrastructure, incident and testing; along with all the possible types of necessary testings. The more checks are implemented along the way, the fewer risks. At the end there is a handy way to quantify your testing maturity level, which can assist in selling the project internally.
Ensure that the deliverable meets business and customer requirements.
In Acceptance Testing, conditions that must be met to satisfy the customer (called Acceptance Criteria) are expressed as an example or usage scenario - called the Acceptance Test. These statements are written from the customer's point of view and explain how a user story or feature should work. In order for the story or feature to be accepted it needs to pass the acceptance criteria; otherwise, it fails. Many times, acceptance tests are automated so they can be performed on all versions of the software. Acceptance criteria usually include one or more acceptance tests.
If your testing framework is suffering, you might want to check if it has these seven quality attributes.
A common problem in software is that developers and designers tend to concentrate on pure functionality and neglect quality attributes. These are the famous “-abilities”: usability, reliability, portability, communicability, testability, reportability, and integratability. Keep these in mind to build a robust automation solution.
Upcoming Events
This site uses cookies so that we can provide you with the best user experience. No cookies are used for marketing purposes - only to perform functions like optimize your navigation, adapt to your preferences,
recognize you each time you visit, and help our team understand which parts of the site you find most
interesting and useful. By continuing to use the website you agree to our cookie policy.