Reference no: EM132366601

Objectives

1. To understand the critical issues in testing.

2. To demonstrate the ability to research and apply proper techniques to conduct white box testing and evaluate the quality of software.

3. To write a proper essay for a specific topic and presenting / arguing the findings.

Problem Statement

Upon satisfactory completion of this assignment you will be able to contribute to industry research and development projects in the context of software engineering, analyze gathered information, and present your findings. To demonstrate your achievement of these goals, you must write a 2,000-word report regarding this test. Your report should consist of the following chapters:

1. A proper title that matches the contents of your report.

2. Your name and Deakin student number in the author line.

3. An executive summary that summarizes your findings.

4. An introduction chapter that explains briefly your chosen white box testing method & tool and the organization of the rest of your report.

5. A chapter details your program tested, which explains in detail different parts of your chosen program including different features, components and functionalities. You may use the same program that you used for Assessment 1 - but this is optional.

6. An analysis chapter that consists of analysis of your white box testing approach, and validity of your testing approaches. If you use unit testing, you should produce results similar to the example shown in week 5's lecture (see slides 47-50). Note that we expect you to focus on analysis of the codes for white-box testing/structural testing, for example, analysis of the paths (McCabe path, Def-Use path) in unit testing and MM path for integration testing, etc. Please refer to Lectures 5-7 and Lecture 9.

7. A test case chapter that lists your test cases and explains why you would use each of them. If you are using user acceptance testing or symbolic execution testing, please lists the user scenario and the test cases you generated from symbolic execution testing.

8. A test demonstration chapter that consists of fully explained screenshots when you use testing tool to conduct the testing tasks. You are required to cover all the bugs you found and document your findings.

9. A conclusions chapter that summarizes major findings of the study and indicates future work which could be conducted in the area.

10. A bibliography list of all cited papers and other resources. IEEE and Harvard are preferred.