Configuring Tests

To configure your tests, follow these steps:

1. Click on the 'Configure' button in the Project page. You can later access this button from the menu button on the top right.
2. In the Project Configuration page, you will see the branches that you had selected.
3. Next, choose a Trigger for your tests. You can choose between 2 options:
   1. Pull Request: Every time you raise a Pull Request in your GitHub repository against your selected Master and Develop branches, Quash will automatically trigger a test on the platform. Quash will scan the PR to identify impacted flows and generate test cases for it.
   2. Slack: If you have the Slack integration set up, you can use slack commands to trigger a test when a PR is raised. Setting up Slack integration is discussed in the 'Other Integrations' section.
4. Next, you need to configure the Test Execution as either 'Auto-run' or 'Review and proceed'. If you choose 'Auto-run', Quash will execute the tests on your connected Device Farm as soon as the scripts and the build are available. If you choose 'Review and proceed', you will need to click on 'Run test execution' button in the Test Details page to start the execution on the Device Farm.
5. The next thing to configure is Application Build. Here you can choose between uploading the application build manually for every test, or if you want Quash to automatically build it from the PR/branch being tested.
6. After this, you can select your Device Farm, and the devices that you want the tests to be executed on. This list of devices available is based on your subscription and plan of the selected Device Farm.
7. Additionally, you can also provide any specific Key and Value pairs that you would want to be used in the script while testing. For example, if there is a specific username and password that you would like to be used while testing the application, specify it as a Key and Value pair. In case of these not being specified, Quash will go on with the testing using default generated values.
8. When you're done, click on the Save button on the top right of the screen. You can now go back to the Project page.

After scanning and configuration is completed, you can now use the selected trigger to run tests within the Project.