Question 6 :
What steps are needed to develop and run software tests?
The following are some of the steps to consider:
â€¢ Obtain requirements, functional design, and internal design specifications and other necessary documents
â€¢ Obtain budget and schedule requirements
â€¢ Determine project-related personnel and their responsibilities, reporting requirements, required standards and processes (such as release processes, change processes, etc.)
â€¢ Identify application's higher-risk aspects, set priorities, and determine scope and limitations of tests
â€¢ Determine test approaches and methods - unit, integration, functional, system, load, usability tests, etc.
â€¢ Determine test environment requirements (hardware, software, communications, etc.)
â€¢ Determine testware requirements (record/playback tools, coverage analyzers, test tracking, problem/bug tracking, etc.)
â€¢ Determine test input data requirements
â€¢ Identify tasks, those responsible for tasks, and labor requirements
â€¢ Set schedule estimates, timelines, milestones
â€¢ Determine input equivalence classes, boundary value analyses, error classes
â€¢ Prepare test plan document and have needed reviews/approvals
â€¢ Write test cases
â€¢ Have needed reviews/inspections/approvals of test cases
â€¢ Prepare test environment and testware, obtain needed user manuals/reference documents/configuration guides/installation guides, set up test tracking processes, set up logging and archiving processes, set up or obtain test input data
â€¢ Obtain and install software releases
â€¢ Perform tests
â€¢ Evaluate and report results
â€¢ Track problems/bugs and fixes
â€¢ Retest as needed
â€¢ Maintain and update test plans, test cases, test environment, and testware through life cycle
Question 7 :
What's a 'test plan'?
A software project test plan is a document that describes the objectives, scope, approach, and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product. The completed document will help people outside the test group understand the 'why' and 'how' of product validation. It should be thorough enough to be useful but not so thorough that no one outside the test group will read it. The following are some of the items that might be included in a test plan, depending on the particular project:
â€¢ Identification of software including version/release numbers
â€¢ Revision history of document including authors, dates, approvals
â€¢ Table of Contents
â€¢ Purpose of document, intended audience
â€¢ Objective of testing effort
â€¢ Software product overview
â€¢ Relevant related document list, such as requirements, design documents, other test plans, etc.
â€¢ Relevant standards or legal requirements
â€¢ Traceability requirements
â€¢ Relevant naming conventions and identifier conventions
â€¢ Overall software project organization and personnel/contact-info/responsibilties
â€¢ Test organization and personnel/contact-info/responsibilities
â€¢ Assumptions and dependencies
â€¢ Project risk analysis
â€¢ Testing priorities and focus
â€¢ Scope and limitations of testing
â€¢ Test outline - a decomposition of the test approach by test type, feature, functionality, process, system, module, etc. as applicable
â€¢ Outline of data input equivalence classes, boundary value analysis, error classes
â€¢ Test environment - hardware, operating systems, other required software, data configurations, interfaces to other systems
â€¢ Test environment validity analysis - differences between the test and production systems and their impact on test validity.
â€¢ Test environment setup and configuration issues
â€¢ Software migration processes
â€¢ Software CM processes
â€¢ Test data setup requirements
â€¢ Database setup requirements
â€¢ Outline of system-logging/error-logging/other capabilities, and tools such as screen capture software, that will be used to help describe and report bugs
â€¢ Discussion of any specialized software or hardware tools that will be used by testers to help track the cause or source of bugs
â€¢ Test automation - justification and overview
â€¢ Test tools to be used, including versions, patches, etc.
â€¢ Test script/test code maintenance processes and version control
â€¢ Problem tracking and resolution - tools and processes
â€¢ Project test metrics to be used
â€¢ Reporting requirements and testing deliverables
â€¢ Software entrance and exit criteria
â€¢ Initial sanity testing period and criteria
â€¢ Test suspension and restart criteria
â€¢ Personnel allocation
â€¢ Personnel pre-training needs
â€¢ Test site/location
â€¢ Outside test organizations to be utilized and their purpose, responsibilties, deliverables, contact persons, and coordination issues
â€¢ Relevant proprietary, classified, security, and licensing issues.
â€¢ Open issues
â€¢ Appendix - glossary, acronyms, etc.
Question 8 :
What's a 'test case'?
â€¢ A test case is a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly. A test case should contain particulars such as test case identifier, test case name, objective, test conditions/setup, input data requirements, steps, and expected results.
â€¢ Note that the process of developing test cases can help find problems in the requirements or design of an application, since it requires completely thinking through the operation of the application. For this reason, it's useful to prepare test cases early in the development cycle if possible.
Question 9 :
What should be done after a bug is found?
The bug needs to be communicated and assigned to developers that can fix it. After the problem is resolved, fixes should be re-tested, and determinations made regarding requirements for regression testing to check that fixes didn't create problems elsewhere. If a problem-tracking system is in place, it should encapsulate these processes. A variety of commercial problem-tracking/management software tools are available (see the 'Tools' section for web resources with listings of such tools). The following are items to consider in the tracking process:
â€¢ Complete information such that developers can understand the bug, get an idea of it's severity, and reproduce it if necessary.
â€¢ Bug identifier (number, ID, etc.)
â€¢ Current bug status (e.g., 'Released for Retest', 'New', etc.)
â€¢ The application name or identifier and version
â€¢ The function, module, feature, object, screen, etc. where the bug occurred
â€¢ Environment specifics, system, platform, relevant hardware specifics
â€¢ Test case name/number/identifier
â€¢ One-line bug description
â€¢ Full bug description
â€¢ Description of steps needed to reproduce the bug if not covered by a test case or if the developer doesn't have easy access to the test case/test script/test tool
â€¢ Names and/or descriptions of file/data/messages/etc. used in test
â€¢ File excerpts/error messages/log file excerpts/screen shots/test tool logs that would be helpful in finding the cause of the problem
â€¢ Severity estimate (a 5-level range such as 1-5 or 'critical'-to-'low' is common)
â€¢ Was the bug reproducible?
â€¢ Tester name
â€¢ Test date
â€¢ Bug reporting date
â€¢ Name of developer/group/organization the problem is assigned to
â€¢ Description of problem cause
â€¢ Description of fix
â€¢ Code section/file/module/class/method that was fixed
â€¢ Date of fix
â€¢ Application version that contains the fix
â€¢ Tester responsible for retest
â€¢ Retest date
â€¢ Retest results
â€¢ Regression testing requirements
â€¢ Tester responsible for regression tests
â€¢ Regression testing results
A reporting or tracking process should enable notification of appropriate personnel at various stages. For instance, testers need to know when retesting is needed, developers need to know when bugs are found and how to get the needed information, and reporting/summary capabilities are needed for managers.
Question 10 :
What is 'configuration management'?
Configuration management covers the processes used to control, coordinate, and track: code, requirements, documentation, problems, change requests, designs, tools/compilers/libraries/patches, changes made to them, and who makes the changes. (See the 'Tools' section for web resources with listings of configuration management tools. Also see the Bookstore section's 'Configuration Management' category for useful books with more information.)