Managing test artifacts

Managing test artifacts involves storing and managing the evidence that has been generated as a part of the test execution phase, or it can also be a set of deliverables generated after any phase of the SDLC.

These artifacts are very useful when managed properly:

• Artifacts generated during defect logging and retesting saves time for both developers and testers, preventing them from having to debug every part of the code, reproducing tests using specified test data, a build version and environment. Log error files, screenshots, database queries with the result set, input parameters, the URL of the application used during testing, the environment, the date tested on, the build number, and so on.
• Deliverables generated after the execution of each phase in the SDLC, such as project charters, BRDs, test plans, RTMs, and test execution reports, often serve as input to the subsequent phase and help teams to focus on the objective and track the progress of a project.
• Other types of artifacts, such as code review or inspection reports, project performance reports, and lessons learned reports, can be useful across the organization and can be used by other team members to make changes to their current strategy. These documents can be part of knowledge base of an organization.
• Training documents, templates (for project management plans, project charters, or requirement specifications) are also part of knowledge management and serve the training needs of new recruits to know more about the organization, its products, and standards followed by them.
• The end user's manual or product-specification documents are usually shared with end users, by the organization, to help them use software or services effectively.

The involvement of testers is not only limited to preparing test data but also preparing and building the knowledge base of an organization and making sure that all the information in the previously listed document is up to date and accurate.