- Tesults Tutorial
- Tesults - Home
- Tesults - Overview
- Tesults - Sign Up & Project Creation
- Tesults - Integrating Your Automated Tests
- Tesults - View Test Results
- Tesults - Team Members
- Tesults - Project Configuration
- Tesults - Actioning Tasks Based on Test Results
- Tesults - Notifications
- Tesults - Integrations with Other Services
- Tesults - Test Case Management with Lists
- Tesults - Test Runs for Manual Testing
- Tesults Useful Resources
- Tesults - Quick Guide
- Tesults - Useful Resources
- Tesults - Discussion
Tesults - Sign Up and Project Creation
This chapter deals with topics such as how to sign up, how to create a project and what exactly are targets in tesults.
Sign up
The first thing to do is sign up. Visit www.tesults.com and click Sign Up from the header.
To sign up, you must enter your email address, create a password and enter your name.
Creating a project
After signing up, you are automatically logged in and can create a project. Click ‘config’ from the header and then click ‘Create New Project’. You need to enter a name for your project.
Next you must choose your plan. For this tutorial, we will create a free project.
After the project is created, a ‘token’ will be displayed. This token is needed to submit test results to Tesults and should be copied. At any time, these token can be recreated from the configuration menu.
At this point the project is created. Next thing to do is integrate automated tests to push results data to Tesults.
Targets
Tesults uses the term ‘target’ to refer to a source of test results data, like a specific test job. The recommendation is to consider each target a bucket to upload test results to. Usually software development teams do not only run a single test run. They may run tests in different environments, on different devices, in different branches and for different modules of an application.
For example, if there is a back-end and a front-end, there may be API tests for the back-end and UI automated tests for the front-end. If these sets of tests are run in a development environment and in a staging environment, then there are four test jobs −
- Back-end development
- Front-end development
- Back-end staging
- Front-end staging
Tesults would consider each one a ‘target’. The reason for this concept of target has to do with making each test run comparable to the last and as a way to organise results data from various sources.