4.1.2.1. Exploratory Test

  • PURPOSE: The purpose of this test is to make sure that the critical defects are removed before the next level of testing starts.

  • TESTERS: QA team.

  • METHOD: This exploratory testing is carried out in the application without any test scripts and documentation.

  • TIMING: At the beginning of each cycle. 

4.1.2.2. Functional Test

  • PURPOSE:  Functional testing will be performed to check the functions of the application. Functional testing is carried out by feeding the input and validating the output from the application.

  • TESTERS: QA Team.

  • METHOD: The test will be performed according to Functional test cases, which are created and stored in TestRail.

  • TIMING: During or after Exploratory test is completed. 

4.1.2.2. End-To-End/User Journey Test

  • PURPOSE: The purpose of this test is to simulate a typical user's journey and interaction with the Mobile App.

  • TESTERS: QA team.

  • METHOD: Ensuring that applications behave as expected and that the flow of data is maintained for all kinds of user tasks and processes. This type of testing approach starts from the end user’s perspective and simulates a real-world scenario. The test will be performed according to End-to-End test cases, which are created using Spreadsheet and stored in JIRA.

  • TIMING: After Functional Test is completed.