Information management projects generally have the following development work:
- Data movement software;
- Data conversion software;
- Data cleansing routines;
- Database development DDL; and
- Business intelligence and reporting analytical solutions.
Module testing validates that each module’s logic satisfies requirements specified in the requirements specification.
- Should focus on testing individual modules to ensure that they perform to specification, handle all exceptions as expected, and produce the appropriate alerts to satisfy error handling.
- Should be performed in the development environment.
- Should be conducted by the software developer who develops the code.
- Should validate the module’s logic, adherence to functional requirements and adherence to technical standards.
- Should ensure that all module source code has been executed and each conditional logic branch followed.
- Test data and test results should be recorded and form part of the release package when the code moves to production.
- Should include a code review, which should:
- Focus on reviewing code and test results to provide additional verification that the code conforms to data movement best practices and security requirement; and
- Verify that test results confirm that all conditional logic paths were followed and that all error messages were tested properly.
- Review design specification with the designer.
- Prepare test plan before coding.
- Create test data and document expected test results.
- Ensure that test data validate the module’s logic, adherence to functional requirements and adherence to technical standards.
- Ensure that test data test all module source code and each conditional logic branch.
- Conduct unit test in a personal schema.
- Document test results.
- Place test data and test results in project documentation repository.
- Check code into the code repository.
- Participate in code readiness review with Lead Developer.
- Schedule code review with appropriate team members.
- Assign code review roles as follows:
- Author, the developer who created the code;
- Reader, a developer who will read the code during the code review—The reader may also be the author; and
- Scribe, a developer who will take notes.
Code Review Procedures
- Validate that code readiness review has been completed.
- Read the code.
- Verify that code and test results conform to data movement best practices.
- Verify that all conditional logic paths were followed and that all error messages were tested properly.
- Verify that coding security vulnerability issues have been addressed.
- Verify that test data and test results have been placed in project documentation repository.
- Verify that code has been checked into the code repository.
- Document action items.
- Unit test data should be created by the developer and should be low volume.
- All testing should occur in a developer’s personal schema.
Unit testing is generally conducted by the developer who develops the code and validates that each module’s logic satisfies requirements specified in the requirements specification.