Test Automation

Walking through the different stages of the development journey and how testing fits into it.

In this short Scrum Tapas video, Professional Scrum Trainer Peter Gfader talks about how testing can different in an agile environment. He walks through different stages, gives some basic recommendations and discusses the works of the team at Growing Agile.

Exploring the world of quality assurance and discussing automated testing for our web and mobile applications.

The Startup Lab host Dave breaks down what automated testing really is and its key benefits to web and mobile applications in this clip. He states that as a software manager your goal is to catch defects before they are shipped to your customers for the best experience possible, to ensure high software quality. A must-watch for all those looking to learn more bout the importance of automated testing and the types of testing.

Describing why you should first define the outcomes before actually crafting a solution.

Ken Pugh leads this informative presentation on ''Shift Testing Left to Build in Quality'' describing how Hypothesis Driven Development (HDD), Behavior Driven Development (BDD), and Test-Driven Development (TDD) work and collaborate for quality assurance. We learn how Shift Left Testing helps build in quality, the different aspects of Shift Left Testing, and how loopbacks and delays are reduced by Shift Left Testing.

Applying the principles of agile development to the practice of testing.

Is it important to test your system's user stories and features before implentation? If YES, why and should it be the FIRST thing to do as an Agile-oriented organization when deploying the system? Agile Testing is a "test-first" approach that applies to all types of agile work to boost the quality of the system before its implementation. It develops and tests systems in small increments, often developing tests before writing the code, Story, or Feature. Let's read the article to find out more.

A visual explanation of the difference between verification and validation, and how they fit into the general concepts of testing.

This visual presentation well explains the difference between verification and validation in software testing. It shows that verification and validation are totally different. Verification focuses on process-related activities while validation focuses on product-related activities. We also learn that verification is done through technical, business, and management reviews while validation is all about unit, integration, system, and acceptance testing.

The importance of "shifting left" from the traditional "V-Model" of testing to gain speed and continuous feedback.

Roman Roth explains the difference between traditional testing and agile testing stating that the former leads to delayed feedback while the latter delivers fast and continuous feedback. He covers how the V-model testing is done, its drawbacks, and how Agile testing is done.

Presenting a detailed difference between test verification vs validation in website testing with examples around cross browser testing.

Arnab Roy Chowdhury deeply explains the difference between verification test and validation test in website/ App testing using cross-browser testing scenarios. He notes that the two testing approaches are not well understood especially by the new testers in the industry. If your interest is to extensively learn about verification and validation testing plus their key difference, then this article is worth reading.

Using Maslow's hierarchy of need as an analogy to define software quality, and to identify which questions to ask for each situation.

The slides showcase how Maslow’s hierarchy of needs theory can be adopted in software development to enhance the quality of a system. Just as people should satisfy the needs at the bottom (Physiological needs) and then up the pyramid till they self-actualize in Maslow’s theory, the same applies to a system to boost its quality. Developers should undergo some levels of tests while also asking the right questions at each stage prior to releasing the system to the users. Check the slides for more details about this approach and how to ask questions for specific situations.

Choosing the right approach to improve the quality of delivery in large agile organizations.

The main objective for an Agile transformation is to promote teamwork for high-quality products and services in an organization. To stay on the track of delivering state-of-the-art products to customers and partners, companies must keep exploring new quality strategies and execute them perfectly. These slides take you through quality strategies and how to employ them in an Agile environment.

How to continuously validate designs to increase predictability in your delivery schedule at a lower cost of quality.

A well-detailed presentation explaining how organizations can leverage continuous verification and validation throughout a systems lifecycle to mitigate business risks. It states that applying verification and validation practices throughout the system's lifecycle helps improve its quality, allowing businesses to converge earlier on the right requirements, compress the time to end-users feedback, and improve their time to market predictability. Take a look at the slides to understand more about how to do the continuous verification and validation approach and its benefits.

By leveraging best practices for Agile performance testing, your IT organization can improve web and mobile application performance.

DevSecOps innovator Alex Weiss comprehensively writes about the 10 best software application performance testing practices that people should consider before jumping into testing. He notes that software application performance testing determines if a system meets certain acceptable criteria for both responsiveness and robustness. He also adds that the process follows a certain protocol and there are also measures that must be taken into account, like simulating production environments to provide much deeper insights into application functionality for the best results. Open the article to learn more about these performance testing best practices from the DevSecOps expert.

Exploring the high returns acquired with the good collaboration between developers, testers and quality assurance.

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.

Everything you need to know to shift left

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.

Elaborate usability tests are a waste of resources. The best results come from testing no more than 5 users and running as many small tests as you can afford.