QA Strategy for the Custom Delivery Application

The company* develops a delivery application with a built-in chat for communication with the support service.

* We recognize the importance of protecting our clients’ privacy and follow the policies to maintain their confidentiality and security. That is why the company name will not be disclosed.

The client has a custom product created from scratch. The functionality of the application keeps growing as the company decides to add new features.

• Our team was to test the functionality of the application to make sure all the features work as supposed and are compatible with different platforms & environments. In particular, we had to check the payment features – the customer balance, the billing process, and the debt generation.
• Another task was to test the Admin Portal. The engineers make sure that the transactions don’t fail after an Admin updates the prices or adds a new item.
• Then, the QA Madness team was to set up the testing process. We were to analyze the requirements and write test documentation, prepare and coordinate the testing activities, and establish communication with the client’s development team.

• After having received a task, we started to prepare test documentation – to write test cases that cover the project requirements.
• When the cases were ready, the team conducted a complete check of the functionality based on these cases. Sometimes we went beyond cases and ran negative tests to detect more defects.
• Each defect was recorded in the testing documentation to use during further testing sessions regularly.
• Sometimes our QA engineers recommended ways to fix a particular defect and advised a solution that would be optimal – that is the most time-efficient and with the least influence on the system as a whole.