Principi de Testare a Software-ului

Software Testing Principles

• Testing Demonstrates Presence, Not Absence of Defects: Testing shows if defects exist, but it cannot guarantee their absence. It reduces the likelihood of undiscovered bugs, but doesn't prove complete correctness.
• Exhaustive Testing is Impossible: Comprehensive testing is impractical, except in trivial cases. Focus on test techniques, prioritization, and risk-based approaches is necessary.
• Early Testing Saves Time and Money: Finding and fixing defects early minimizes subsequent problems and reduces overall costs. Static and dynamic testing should start early in the software development life cycle (SDLC).
• Defects Cluster Together: Many bugs reside in a small percentage of components. This Pareto principle helps prioritize risk-based testing. Observed defects aid in testing strategy.
• Tests Wear Out: Repeated tests become less effective at uncovering new defects. Revise existing tests and create new ones to maintain high test effectiveness. Repeating tests can be beneficial, such as in automated regression testing.
• Testing is Context Dependent: No single testing approach fits all situations. Testing strategies must adapt to the specific context.
• Absence-of-Defects Fallacy: Focusing solely on verification might not guarantee a successful system. Validation is also essential to ensure user needs and business objectives are met. A good system fulfills intended functionalities and surpasses competitors.

Test Activities and Tasks

• Test Planning: Defines objectives and selects the optimal testing approach within constraints.

• Test Monitoring and Control: Continuously tracks progress against the test plan and takes corrective actions.

• Test Analysis: Examines the test basis to identify testable features, define test conditions, prioritize them, and assess risks. This includes evaluating the potential defects in test objects and their testability. It also helps determine "what to test" using quantifiable coverage criteria.

• Test Design: Translates test conditions into test cases and creates other necessary test artifacts. Determines necessary test data and sets up the testing environment, identifying required infrastructure and tools. "How to test?" is the focus of this stage.

• Test Implementation: Develops or acquires test artifacts (test data, scripts), organizes test cases into procedures and suites, and establishes a test execution schedule.

• Test Execution: Runs the tests as per the schedule. Manual or automated execution may be used. Compare actual results with expected results. Logs results, analyzes anomalies, and reports failures.

• Test Completion: Occurs at project milestones to address outstanding issues. Archives reusable testware, shuts down the test environment, identifies lessons learned, and prepares a report to stakeholders.