Software Reviews & Testing

What's the principal objective of Software Reviews?

• Run individual test.

• Show my work progress

• Get approvals for my configuration or development.

• Find and remove defects on early phases.

Each team member use it to review his or her work products, like a user stories specification, simple design, configuration, code or test case.

• Passaround

• Team Review

• Individual Review

• Inspection

• Walkthrough

What's a Peer Deskcheck?

• Sends a copy of the product to multiple people and collects defects.

• A single person other than the author examines the work product and send a list of defects.

• The author describes his product to a set of colleagues, requests and collects their defects.

• It consists in: Planning, Preparation, Board, Correction of Defects, Follow-up to Correction and Causal Analysis.

Software Reviews and Testing are the same?

• Yes.

• No.

What is Testing?

• A planned series of checks.

• Verify that system is constructed in accordance with approved requirements.

• Validate that they support the intended business needs.

• All of the above.

What's the name of test that runs the developers?

Is the process of testing user stories specifications to verify the application is performing to specification.

• Integration Test

• User Acceptance Test

• System Test

• Regression Test

What's Integration Test?

• The process of verifying all components of the application in a fully integrated testing environment that mimics the real world use, including the interaction with external systems.

• The process of testing series of units of functionality to verify they work or communicate with each other within a specific application.

What are the principal artifacts of Testing?

• Defect Log

• Checklists

• Test Scenarios

• Test Cases

• Test Scripts

What are the principal artifacts of Software Reviews?

• Test Case

• Defect Log

• Checklists

• Standards