Setting up projects
Upon logging in, you'll see a clean and intuitive dashboard with three primary tabs:
- Projects:
- A container for repositories and applications integrated with the SDK.
- Houses automated tests and bug tickets for specific projects.
- Automated tests:
- A comprehensive view of all automated tests across projects.
- Provides insights into test performance and coverage.
- Tickets:
- A centralized view of all reported bug tickets across projects.
- Enables efficient tracking and resolution.
You can begin setting up your first project by:
- Clicking on the 'Create a project' button on the top right of the screen.
- You will see a popup with 2 text fields - Project ID and project name. Your Project ID will be auto-generated and populated in the first field. You will not be able to edit it. The ID number will keep increasing in sequence for every new project that you create.
- Enter a project name (ideally, the name of the app or the repository you will be testing within this project)
- Confirm by clicking on the 'Create project' button.
After creating the project, you have 2 options:
Automation testing - To proceed with automation testing you will need to connect your project to a version control system, trigger scan and configure a device farm to enable automated testing. This will be discussed in the Quash Automate section.
Manual bug reporting - To proceed with this, you will have to integrate our Quash SDK, into your application. This integration allows it to automatically capture issues and generate detailed bug tickets during real-world usage. This will be discussed in the Quash Report section.
After creating a project, you can choose to either automated tests or generate bug tickets based on your project requirements. You are not required to complete both immediately.
However, a project can have both these linkages, and ideally, they should be associated with the same application. If you choose to do one first, you will still have the option to complete the other later.
