# How to create a test case?

Every test step begins with an action. These actions are pre-built functions to mimic user interactions like clicking, typing, etc,

**How to perform a click action?**

1. Choose the "Click" action.
2. Select the element type like button, link, etc.
3. Enter the element name (e.g., 'Login', 'Add Ticket').

<figure><img src="/files/UKmGIRllgThd3hRaFWyD" alt=""><figcaption><p>click action</p></figcaption></figure>

&#x20;**Note:** The element name should match exactly, and it is case-sensitive.

**How to type in an input field?**

1. Choose the "Type in fields with" action.
2. Select the input field by its "Placeholder" or "Label".
3. Enter the placeholder or label value.
4. Enter the value to be filled in the input field.

<figure><img src="/files/re4IyqFNhlwP6xxmF0Dt" alt=""><figcaption><p>type action</p></figcaption></figure>

&#x20;**Note:** You can also perform actions on elements using their "id" and "CSS class name".


# Test Suites

Test cases can be grouped under test suites according to their structure. For example, If you have test cases for Login functionality, you can create a test suite called "Login" and add all the test cases related to the login functionality under the suite and execute the suite. This helps when testing a specific functionality alone.&#x20;

**How to create a test suite?**

1. Navigate to the Test Suite section&#x20;
2. Click the '+' button and then provide a name for the suite and save the suite.

<figure><img src="/files/2k1gZ9iaoBUliqGLmhqI" alt=""><figcaption><p>create a test suite</p></figcaption></figure>

**How to associate a test to a suite?**

1. Open a test case
2. On the right side panel, Click the test suites field
3. Type the suite name and then select the suite.

<figure><img src="/files/FdcHSonP13wHazzkagXW" alt=""><figcaption><p>associate test case to a test suite</p></figcaption></figure>

**Note :**&#x20;

1. You can associate a test case with multiple test suites&#x20;


# Test Data

Test data in SprintsQ is essential for reusing data across multiple tests, ensuring efficiency and consistency. When you edit test data, the changes automatically propagate to all associated test cases.

**Types of Test Data in SprintsQ:**

* **Text:** This type can hold any text-based information such as page URLs, element names, test credentials, and more.
* **State:** A 'state' captures all relevant data like cookies and local storage from a webpage. To record a state, you must replicate the same navigation steps as when creating a test case. For instance, modern web applications typically store user information in cookies and local storage, enabling automatic login without re-entering credentials. Utilizing 'state' test data can bypass repetitive login steps across test cases.

**Creating Test Data:**

1. Select the 'Test Data' option from the left panel.
2. Click on the '+Test Data' button to start the process.

*Notes:*

* Users must possess the appropriate permissions with 'test data creation' rights to create test data.
* The values within a 'state' type are not visible to the users for security and privacy reasons.

By using test data effectively, you can streamline your testing process and avoid unnecessary repetition in your test cases.


# Examples

<mark style="color:red;">**Sample Login with correct credentials**</mark>&#x20;

<figure><img src="/files/G9rkhZCdq7RXpvQExdDF" alt=""><figcaption></figcaption></figure>


# Settings

Settings in software development refer to configurable options or parameters that allow users or developers to customize the behavior and functionality of a software application. These settings are essential for tailoring the software to meet specific requirements, preferences, or environmental constraints. SprintsQ provides the options to import and export settings to facilitate backups, sharing configurations, or setting up software on multiple devices.

<br>


# My Info

Users can update his/her personal details. Further, it shows the number of projects the user is involved in.&#x20;

<br>


# Organizations

* **Company:** Tells about the subscription plan, its validity, number of users, and projects involved in it
* **Users:** Gives basic information about the members of your company. Users can be added to respective projects or removed only by the admin (i.e.)  user with setting update permission access. Admin can only update the information about the other user. A user with prior access can only view the records of the respective projects.
* **Projects:** Gives information about the various projects present in the company. Projects can be created and modified only by the Admins and users with setting update permission access.&#x20;
* **Roles:** When a user is added to SprintsQ, he/she can access the SprintsQ modules based on their roles. By default admin and Guest user roles will be created once you sign up. You can create a custom role with a set of permissions and assign the role to a user in user sections. There are 4 permission modes for each module - view, create, update, and delete.


# Trash

When a bug is no longer needed, it can be deleted. Deleted items will be moved to the trash. If a bug is needed again, it can be restored from the trash. If it's not necessary, it can be permanently deleted from the trash.