Question 4: Chapter 22-Testing Strategies IFM16 EXAM

Discuss Testing Strategies for OO?

-Class testing is the equivalent of unit testing. Operations within the class are tested. The state behavior of the class is examined.

Fully Discuss WebApp Testing Strategies?

1. WebApp content model is reviewed to uncover errors. 2. Interface model is reviewed to ensure all use-cases are accommodated. 3. Design model for WebApp is reviewed to uncover navigation errors. 4. User interface is tested to uncover presentation errors and or navigation mechanics problems. 5. Selected functional components are unit tested. 6. Navigation throughout the architecture is tested. 7. WebApp is implemented in a variety of different environmental configurations and the compatibility of WebApp with each is assessed. 8. Security tests are conducted. 9. Performance tests are conducted. 10. WebApp is tested by a controlled and monitored group of end-users.

Testing strategies of OO also include what? extend more?

OO also include : 1.Thread-based testing—integrates the set of classes required to respond to one input or event. 2.Use-based testing—integrates the set of classes required to respond to one use case. 3.Cluster testing—integrates the set of classes required to demonstrate one collaboration.

Fully Discuss Smoke testing as part of Integration testing.

•Commonly used when product software is developed. •Good for time-critical projects as it allow software teams to asses' projects on frequency basis. 1. Software components already translated into code are integrated into a build. 2. A series of tests designed to expose errors that will keep the build from performing its functions are created. 3. The build is integrated with the other builds and the entire product is smoke tested daily (either top-down or bottom integration may be used).

Discuss Unit Test Considerations provide Diagram?

•Data flow across component interface is tested before any other testing is initiated

Consider Object-Oriented Test, Fully Discuss Integration Testing in Context of OO?

•Focuses on groups of classes that collaborate or communicate in some manner. •Integration of operations one at a time into classes is often meaningless.

Discuss Unit Testing?

•Focuses on smallest unit of software design - the software component or module, Module interfaces are tested for proper information flow, Boundary conditions are tested. •Basis independent path are tested, all error handling paths should be tested, and Drivers and or stubs need to be developed to test incomplete software.

List some Benefits of Smoke testing?

•Integration Risk is minimized. •Quality of product is improved. •Error diagnosis and correction is improved. •Progress is easier to assess.

Fully Discuss Integration Testing?

•Sandwich testing uses top-down tests for upper levels of program structure coupled with bottom-up tests for subordinate levels •Testers should strive to identify critical modules having the following requirements •Overall plan for integration of software and the specific tests are documented in a test specification •Some strategies include Top-down integration testing, Bottom-up integration testing, Regression testing, Smoke testing.

Consider Object-Oriented Test, Fully Discuss Unit Testing in Context of OO?

•Smallest testable unit is the encapsulated class or object. •Similar to system testing of conventional software. •.do not test operations in isolation from one another •.Driven by class operations and state behavior, not algorithmic detail and data flow across module interface.

Defined Characteristics of Testing strategies based on developer's view?

•Testing begins at the component level and works outward toward the integration of the entire computer-based system. •The developer of the software conducts testing and may be assisted by independent test groups for large projects. •Testing and debugging are different activities. •Debugging must be accommodated in any testing strategy.

Fully discuss Strategic Approach to Software Testing?

•This are set of activities that can be planned systemically to test software, a software testing template should be defined for the software process. •Strategies for testing must accommodate low level tests that are necessary to verify small source code segment has been implemented correctly as well as high level tests. •Strategies should provide guidance for practitioner and set mile stone for manager.

Fully discuss validation testing?

•Validation tests are based on the use-case scenarios, the behavior model, and the event flow diagram created in the analysis model. Must ensure that each function or performance characteristic conforms to its specification. Deviations must be negotiated with the customer to establish a means for resolving the errors.

Discuss Testing strategies for conversational software, i.e. Testing Issues?

•Wait until the end before testing, if it doesn't work, why? •Test Daily understand problems. •Specify product requirements in a quantifiable manner before testing starts. •Specify testing objectives explicitly. •Identify categories of users for the software and develop a profile for each. •Develop a test plan that emphasizes rapid cycle testing. •Build robust software that is designed to test itself. •Use effective formal reviews as a filter prior to testing. •Conduct formal technical reviews to assess the test strategy and test cases. •Develop a continuous improvement approach for the testing process.