Verification Process in Database Operations Using algoQA

TABLE OF CONTENTS

1. Overview

2. Supported Databases

3. Parameterization to verifying User Credentials

3.1 Scenario 1 Providing a Specific Parameter for a User

3.2 Scenario 2: Using a Global Variable for Parameter

1. Overview

You can leverage agoQA to verify user credentials, confirming that the data is correct and exists in the database.

Once the verification process confirms the data’s validity, the system proceeds to execute the necessary database operations. These operations may involve querying the database for existing user information, validating input, and inserting the new user’s data if the credentials pass the checks.

2. Supported Databases

Database Name	Database Description
Mongo DB	A NoSQL database that stores data in flexible, JSON-like documents. It is known for its scalability and flexibility, making it suitable for applications with rapidly changing data models.
SQL (Structured Query Language)	SQL is a standard language for managing relational databases. It is used for querying and manipulating data stored in relational database management systems (RDBMS) like MySQL, PostgreSQL, and others.
PostgreSQL	An advanced open-source relational database management system with a strong focus on features, standards compliance, and extensibility. It supports various data types, indexing techniques, and features, such as JSON support and advanced indexing
Redshift	A fully managed data warehouse service provided by Amazon Web Services (AWS). It is optimized for data analysis queries on large datasets and is commonly used for business intelligence and data analytics purposes.
MySQL	An open-source relational database management system based on SQL. It is widely used for web applications and known for its reliability, ease of use, and performance.

3. Parameterization to verifying User Credentials 

For verifying the parameters, navigate to the Node configuration, you can either provide test data or parameter in the UI element control value text box. For providing parameters, refer to the article Producing Meaningful GWT steps.

3.1 Scenario 1 Providing a Specific Parameter for a User

Enter a fixed parameter value (for example, "John") in the UI element control to be used during node configuration.

Perform the following:

1. Navigate to the Node Configuration section.
2. Locate the UI element control labeled "username" (or similar).
3. In the text box provided, enter the specific value "John".
4. The system will now use "John" as the username for the test.
5. Save the configuration.
6. Run the test to verify that John is used in the test case for the Username field and displayed in the example table of the feature file.

Expected Outcome:

The test should automatically input "John" as the username wherever it is referenced and display in the Feature File.

3.2 Scenario 2: Using a Global Variable for Parameter

Use a global variable (for example <username>) that can dynamically take different values for various test cases.

Perform the following:

1. Navigate to the Node Configuration section.
2. Locate the UI element control for "Username".
3. In the text box provided, instead of entering a fixed value, enter the global variable placeholder <username>.
4. Define the global variable <username> in the global configuration (or as part of a parameterized test).
5. Example: <username> can be defined with values like "John", "Alice", or "Bob" depending on the test case.
6. Save the configuration.
7. Run the test and observe how the system automatically uses the value associated with the <username> global variable.

Expected Outcome:

The platform dynamically replaces <username> with the defined value (for example., "John", "Alice", or "Bob") as per the global configuration.

This allows multiple tests to be executed with different values for Username without modifying the test script manually.