At 383, we are committed to delivering high-quality products, services, and processes that meet or exceed the expectations of our customers. We believe that quality is everyone's responsibility, and we are dedicated to maintaining a culture of continuous improvement and accountability.
This Quality Assurance Code of Conduct outlines the principles and best practices that we expect all team members to adhere to in order to ensure that we consistently deliver products and services of the highest quality. By working together and upholding these standards, we can achieve our goal of providing exceptional value to our customers while maintaining the highest levels of quality.
This code of conduct contributes as part of our main engineering code of conduct which can be found here:
Engineering code of conduct homepage
Manual quality assurance (QA) is a process of verifying that a product or service meets a set of predetermined quality standards through manual inspection and testing. In this process, trained human testers examine the product or service to identify any defects or issues that may negatively impact the user experience.
Manual QA typically involves the following steps:
-
Defining the requirements: The first step is to define the quality standards or requirements that the product or service must meet. These requirements can include functional requirements, performance requirements, security requirements, usability requirements, and so on.
-
Designing test cases: Testers create test cases that outline the specific steps they will take to test the product or service against the defined requirements. Each test case typically includes a set of inputs, expected outputs, and the expected behavior of the product or service.
-
Executing test cases: Testers manually execute the test cases, following the steps outlined in each one. They observe the behavior of the product or service and record any issues or defects that they encounter.
-
Reporting and tracking defects: Testers report any issues or defects they find during testing and track them until they are resolved.
At 383 our QA process involves all of these and more.