Test Library Management includes:
- change control to assure that changes are made only by authorized personnel, are documented.
- version control; to assure that tests for different versions of the same application are kept segregated.
- configuration management to account for any changes to the test environment.
Change control
- refers to the orderly process of introducing change to the test library.
Documentation is the key:
- Changes may take form of new tests being added or existing tests being modified or deleted.
- Documentation of the nature of the change to existing module should include the delta file, which contains the difference between the old module and the new one.
- Explanation should be provided of what was changed and where.
Change log:
- Test librarian should manage the change control process, keeping either written or electronic log of all changes to test library.
- Change log should list each module affected by the change, nature of the change, person responsible, and date and time.
- Regular backups of the test library are critical, so erroneous changes can be backed out if needed.
Test your tests:
- Test being added to the library should be tested as well.
- It should have been executed atleast once before being introduced into permanent library.
Synchronize with source control:
- There should also be some level of correspondence between the change log for application source and test library.
- It is ideal to use same source control system whenever possible.
- If the change to test results a new capability in different application version, then new test should be checked into different application version, then new test should be checked into different version of the test library instead of overwriting the test for prior version.
Version Control:
Just as the application source code must be kept aligned by versions, so must the test library.
Multiple application versions:
- At any given point, more than one version of the application may require testing; for example, fixes may be added to the version in the field, while enhancements are being added to the new version planned for the release.
Multiple test library versions:
- Proper version control of test library allows test execution cycle to be performed against corresponding version of application without confusing changes made to tests for application modifications in subsequent versions.
- change control to assure that changes are made only by authorized personnel, are documented.
- version control; to assure that tests for different versions of the same application are kept segregated.
- configuration management to account for any changes to the test environment.
Change control
- refers to the orderly process of introducing change to the test library.
Documentation is the key:
- Changes may take form of new tests being added or existing tests being modified or deleted.
- Documentation of the nature of the change to existing module should include the delta file, which contains the difference between the old module and the new one.
- Explanation should be provided of what was changed and where.
Change log:
- Test librarian should manage the change control process, keeping either written or electronic log of all changes to test library.
- Change log should list each module affected by the change, nature of the change, person responsible, and date and time.
- Regular backups of the test library are critical, so erroneous changes can be backed out if needed.
Test your tests:
- Test being added to the library should be tested as well.
- It should have been executed atleast once before being introduced into permanent library.
Synchronize with source control:
- There should also be some level of correspondence between the change log for application source and test library.
- It is ideal to use same source control system whenever possible.
- If the change to test results a new capability in different application version, then new test should be checked into different application version, then new test should be checked into different version of the test library instead of overwriting the test for prior version.
Version Control:
Just as the application source code must be kept aligned by versions, so must the test library.
Multiple application versions:
- At any given point, more than one version of the application may require testing; for example, fixes may be added to the version in the field, while enhancements are being added to the new version planned for the release.
Multiple test library versions:
- Proper version control of test library allows test execution cycle to be performed against corresponding version of application without confusing changes made to tests for application modifications in subsequent versions.
No comments:
Post a Comment