Quality Assurance Engineers
Introduction
Quality Engineers play an essential role in ensuring that software products meet the highest quality standards. Their responsibilities include creating comprehensive test plans, designing test cases, setting up test environments, executing tests, and more. This document outlines the key activities and best practices for Quality Engineers to ensure thorough and efficient testing processes.
Capturing Compliance Evidence with surveilr
Resource surveillance (surveilr
) provides the file ingestion command for QA engineers to execute. This command captures compliance evidence from Work Product Artifacts (WPAs) and store them in a Resource Surveillance State Database (RSSD) named resource-surveillance.sqlite.db
, under the uniform_resource table.
Evidence Types
- Compliance Evidence: Shows adherence to policies.
- Non-Compliance Evidence: Indicates violations of policies.
Common Commands
-
To ingest files in the current directory:
-
To run queries in RSSDs:
Examples of Work Product Artifacts (WPAs)
Creating a Test Plan
A company’s policy might state: “All quality engineers must create a detailed test plan for each project.” This policy can be broken down into the following requirements:
- Outline the testing approach, objectives, scope, resources, and timelines.
- Ensure the test plan is documented and accessible to all stakeholders.
Using surveilr
for Policy Compliance and Evidence Capture
The next step is to use surveilr
to ensure compliance with these policies, capturing the necessary details and storing them under the database table.
SQL Query for Verification of Test Plan Compliance
Compliance Evidence
Host Name | Test Plan |
---|---|
HostName_1 | Detailed Plan 1 |
HostName_2 | Detailed Plan 2 |
Non-compliance Evidence
Host Name | Test Plan |
---|---|
HostName_1 | |
HostName_2 |
Designing Test Cases
A company’s policy might state: “All quality engineers must design test cases based on functional and non-functional requirements.” This policy can be broken down into the following requirements:
- Base test cases on user stories and acceptance criteria.
- Ensure test cases cover all relevant functionalities.
Using surveilr
for Policy Compliance and Evidence Capture
The next step is to use surveilr
to ensure compliance with these policies, capturing the necessary details and storing them under the database table.
SQL Query for Verification of Designing Test Cases
Compliance Evidence
Host Name | Project Name | Test Cases |
---|---|---|
HostName_1 | project-1 | Comprehensive |
HostName_2 | project-2 | Comprehensive |
###$ Non-compliance Evidence
Host Name | Project Name | Test Cases |
---|---|---|
HostName_1 | project-1 | |
HostName_2 | project-2 |
Setting Up Test Environments
A company’s policy might state: “All quality engineers must set up test environments that closely resemble the production environment.” This policy can be broken down into the following requirements:
- Set up staging environments for testing activities.
- Ensure environments are regularly updated and maintained.
Using surveilr
for Policy Compliance and Evidence Capture
The next step is to use surveilr
to ensure compliance with these policies, capturing the necessary details and storing them under the database table.
SQL Query for Verification of Setting Test Environments
Compliance Evidence
Host Name | Environment Name | Setup Details |
---|---|---|
HostName_1 | staging-1 | Detailed Setup 1 |
HostName_2 | staging-2 | Detailed Setup 2 |
Non-compliance Evidence
Host Name | Environment Name | Setup Details |
---|---|---|
HostName_1 | staging-1 | |
HostName_2 | staging-2 |
Manually Executing Test Cases
A company’s policy might state: “All quality engineers must manually execute test cases to validate functionality, usability, and user interface.” This policy can be broken down into the following requirements:
- Execute test cases manually.
- Document the results of each test execution.
Using surveilr
for Policy Compliance and Evidence Capture
The next step is to use surveilr
to ensure compliance with these policies, capturing the necessary details and storing them under the database table.
SQL Query for Verification of Manual Test Execution
Compliance Evidence
Host Name | Test Case Name | Execution Results |
---|---|---|
HostName_1 | test-case-1 | Pass |
HostName_2 | test-case-2 | Pass |
Non-compliance Evidence
Host Name | Test Case Name | Execution Results |
---|---|---|
HostName_1 | test-case-1 | Fail |
HostName_2 | test-case-2 | Not Executed |
Developing and Executing Automated Test Scripts
A company’s policy might state: “All quality engineers must develop and execute automated test scripts to improve efficiency.” This policy can be broken down into the following requirements:
- Automate repetitive and time-consuming testing tasks.
- Increase test coverage with automated scripts.
Using surveilr
for Policy Compliance and Evidence Capture
The next step is to use surveilr
to ensure compliance with these policies, capturing the necessary details and storing them under the database table.
SQL Query for Verification of Automated Test Scripts
Compliance Evidence
Host Name | Project Name | Automation Script |
---|---|---|
HostName_1 | automation-project-1 | Pass |
HostName_2 | automation-project-2 | Pass |
Non-compliance Evidence
Host Name | Project Name | Automation Script |
---|---|---|
HostName_1 | automation-project-1 | Fail |
HostName_2 | automation-project-2 | Not Executed |
Performing Regression Testing
A company’s policy might state: “All quality engineers must perform regression testing to ensure new changes do not affect existing functionality.” This policy can be broken down into the following requirements:
- Execute regression tests after every code change.
- Document any issues found during regression testing.
Using surveilr
for Policy Compliance and Evidence Capture
The next step is to use surveilr
to ensure compliance with these policies, capturing the necessary details and storing them under the database table.
SQL Query for Verification of Regression Testing
Compliance Evidence
Host Name | Project Name | Regression Script |
---|---|---|
HostName_1 | regression-project-1 | Pass |
HostName_2 | regression-project-2 | Pass |
Non-compliance Evidence
Host Name | Project Name | Regression Script |
---|---|---|
HostName_1 | regression-project-1 | Fail |
HostName_2 | regression-project-2 | Not Executed |
Conducting Performance Testing
A company’s policy might state: “All quality engineers must conduct performance testing to evaluate the application’s performance.” This policy can be broken down into the following requirements:
- Use appropriate tools for performance testing.
- Document the performance benchmarks and test results.
Using surveilr
for Policy Compliance and Evidence Capture
The next step is to use surveilr
to ensure compliance with these policies, capturing the necessary details and storing them under the database table.
SQL Query for Verification of Performance Testing
Compliance Evidence
Host Name | Project Name | Performance Script |
---|---|---|
HostName_1 | performance-project-1 | Pass |
HostName_2 | performance-project-2 | Pass |
Non-compliance Evidence
Host Name | Project Name | Performance Script |
---|---|---|
HostName_1 | performance-project-1 | Fail |
HostName_2 | performance-project-2 | Not Executed |