Types of requirements may include: | functional, such as audio and visualinstallation, such as new, upgrades, database and softwarenon-functional, such as performance, load, stress and culturalplatform or environment. |
Outstanding bugs may include: | defined prioritieswith or without defined priorities. |
Limited release may include: | alpha and beta release optionsenvironment-specific releaseinternal or in-house release optionsexternal release optionsplatform-specific release. |
Test cycles may include: | delivery of testable product to clientdelivery of testable product to test teamin-development tests, such as source-code updates or retrievals from source control, initial implementation complete time, pre-implementation time. |
Types of testing may include: | acceptancedata functionalityfunctionalitygraphical user interface (GUI)loadperformanceregressionsmokestressunit. |
Testing methods may include: | automated, such as coded testing or using automation-toolmanual, such as exploratory or testing of specific test casesstatic and dynamic analysis. |
Testing technique may include: | boundary value analysisequivalenceway of designing test cases. |
Test-support software may include: | bug tracking softwaretest automation software, such as:WinRunnerLoadRunnertest case-management software, such as Test Director. |
Implementation details and reporting details may include: | communication and interaction levels between departments for cycles, such as development may or may not be approachable during particular processes or cyclesdetails of all processes and proceduresrequired documentation repositories, templates, structures and locations. |
Completeness techniques may include: | interdepartmental reviewsintradepartmental reviewssystem dissection. |