Improving Application Quality With a Simplified QA Approach

The Quality Assurance Team (QA Team) is responsible for delivering quality products and facilities. It is made up of QA analysts and QA engineers.

The QA team works closely with everyone involved in developing new features or any modifications affecting the code. By this, we mean that we help product owners and designers shape the best features of the future. We also help ensure that the full scope of features was implemented during and after developers development. To sum up, our job is not just to test the app after a new increment, Rather helping the entire team provide the best services for our users.

Now that we have defined the QA task, let's move on to 3 steps that will help you provide new features without any fear:

1 - Know your product and create an efficient regression test suite

2 - Create test strategies for all the new features you are developing

3 - Conducting an efficient testing session

Step 1: Know your product and create an efficient regression test suite

The very first step is a one-time job that may seem a bit fast at first glance, but that will be the foundation of your cue job. The idea is simply to write down all possible scenarios of your service and then select the most important ones.

The goal of this task is to:

1. Conduct better QA work;

2. Make sure you do not forget to use those cases when you test our app and especially new features.

Step 2: The creation of test strategies.

After the first phase is complete, you are about to move to another location, which involves creating test strategies for all the new features you are developing.

Test strategies do not simply consist of new test cases. They should also have hints about feature testability. Meaning, all the necessary information that will help the testers to test the facility.

Once the test strategy is valid, we share it with the product owner, to ensure that we have understood the specs correctly. We also share it with developers who will work on the feature, taking into account all the scenarios for them, even before coding the new feature.

At the end of the day, test strategies are initiated by QA analysts but are made by each member of the team. This is a living document that should be adapted even when the specs change or a forgotten test case is discovered.

Step3: Conducting an efficient testing session

When the test strategy is validated and shared with everyone, the QA team is ready to test the facility. While we wait for development to take place, this is a good time to start new testing strategies.

A few days after the test strategies are validated, the developer will come to you and say "Hey, I've worked with the new feature, let's test it!".

This is a great moment for everyone to be involved in the trial efforts, ensuring that it was developed visually and technically.

To conduct a test, the QA analyst who is responsible for the feature must first assign test cases to the examiners. This means distributing each test case to participating testers. This facilitates testing sessions and helps ensure that we do not forget test cases.

During this testing session, especially the first one, we can find bugs and later create bug tickets for developers to fix them. Once the bugs found are fixed, we organize a new test session so that all the test cases of that new feature revisit. And this was until all the insects were found and fixed.

After that, and only when all the test cases pass successfully, we consider this feature valid. Then we can move on to the last and final step, which involves making sure that the new version does not have regression.

The idea here is to organize a new test session, which includes making sure that the integration of the new feature and/or bug fixes does not break existing parts of our application.

To do this, we test:

1. All test cases in the application that are identified as regression test cases

2. All new test cases created by the new functionality that is in the tested version

3. All other test cases related to code modification, and will not be regression test cases nor related to new functionality. For example, if the above bug regarding profile picture modification was fixed.

We provide end-to-end ERP development and integration services to streamline enterprise processes and enhance workflow efficiency. Our team uses open-source tools and ERP platforms to custom build feature-rich enterprise applications from the ground up to solve complex business problems.