More topics

NRM SDLC - Quality Assurance and Testing

Last updated on April 11, 2024

Quality Assurance (QA) testing standards are established to ensure the quality, reliability, and consistency of software testing processes. QA standards are methodology agnostic, meaning they are designed to be applicable and adaptable to various software development methodologies and practices.  These standards provide a framework for establishing quality assurance processes, principles, and best practices, regardless of which methodology is followed (e.g., Waterfall, Agile, other). 

Expand All | Collapse All
 

Test Strategy

All NRM IT projects must document a Test Strategy.

A Test Strategy is a high-level outline that describes the overall approach, goals, and objectives for testing a software application or system.

 

Test Plan

All NRM IT projects must document a Test Plan.

A Test Plan is a detailed outline that specifies the test activities, tasks, deliverables, schedules, and responsibilities for testing a software application or system.

 

Test Execution

All test cases must be executed as determined by the Test Plan and test results documented.

Test case execution involves running the predefined test cases against the software or system to assess its behavior, functionality, and performance.

 

Unit Testing

Unit Testing must be conducted during development of an application and results logged.

Unit Testing, also known as Component Testing, is a level of software testing where individual units or components of a software are tested.

 

System and Integration Testing

System and Integration Testing (SIT) must be conducted and test results documented.

System and Integration Testing is a level of software testing that focuses on testing the entire system and/or application as a whole.

 

User Acceptance Testing

Business representatives must conduct User Acceptance Testing (UAT) and are responsible for UAT sign-off.

User Acceptance Testing is a type of acceptance testing performed to determine if intended users accept the system.

 

Deployment Verification Testing

A Deployment Verification Test (DVT) must be conducted as part of the deployment.

Deployment Verification Testing, also known as a Build Verification Test or Smoke Test, focuses on validating that the software or system has been successfully deployed to an environment and functions as expected in that specific environment.

 

Production Verification Testing

Business representatives must conduct Production Verification Testing (PVT) and are responsible for PRODUCTION sign-off.

A Production Verification Test is a test to ensure that the live build is working as intended in its final environment.

 

Defect Management

Defects must be recorded and managed systematically.

Defect Management is a systematic process of identifying, documenting, prioritizing, tracking, and resolving defects or issues that are discovered during the software development and testing phases.

 

 

Contact information

Please contact us via email for any inquiries related to the SDLC.

NRIDS Standards Enquiries
NRIDS.Standards@gov.bc.ca