Software Testing & Quality Assurance Give answers to the following questions in your own words . Please leave the questions in your document and place your answer directly below. please remember to...

Software Testing & Quality Assurance
Give answers to the following questions in your own words. Please leave the questions in your document and place your answer directly below. please remember to use proper notation and citations, EVEN for our course textbook. With the exception of #4, an appropriate response to each question will be about 500-600 words; the answer to number #4 will likely be shorter.
I. A company uses the following metric to gauge product quality. Once a bug is reported, that same bug is closed if it cannot be recreated by the testing team. Naturally, this lead to a high defect fix rate. concisely identify at least two problems with this approach. As the testing manager, how would you modify this plan to more accurately reflect product quality?
The problems associated with the debugging approach are as follows:
· Finding the cause of the e
or is difficult for the testing team
· Suspected causes exist for the problem.
· The cause is suspected by the team. Test cases are designed to validate the suspicion.
· E
ors are co
ected iteratively.
· Many tests are ca
ied out to find the e
ors.
· Hence, there will be high defect fix rate.
The problem can be co
ected by the following modifications:
· The testing team must try to find the symptom and cause of the problem.
· Many test cases must be run.
Some of the problems with the debugging approach are discussed below:
· The symptom and the cause are present in geometrically remote places.
· The symptom occurs in one portion of the program, But the cause of the e
or is placed at a remote site.
· The problem is removed temporarily when a different e
or is detected and removed.
· The problem is due to non-e
ors such as round-offs and inaccuracies.
· Human e
ors cause the problem. They are not easily traced.
· Inaccuracy in the Input data.
· The problem occurs intermittently.
· The problem is due to distribution of number of tasks on different processors.
· The type of e
ors are determined and removed and the plan is modified accordingly and quality product is obtained.
Debugging results from testing. The test cases are executed. The expected results and the actual results are obtained. The debugging process matches the symptoms with cause and attempts to remove the e
or. E
ors range from mild e
or to catastrophic e
ors. The three debugging strategies:
1) Debugging using Brute Force approach
2) Debugging by Backtracking approach
3) Debugging by Cause Elimination approach
The debugging strategy are done manually or by using debugging tools.
Brute Force Technique
It is the general method of software e
or detection. It is less efficient debugging method It is applied when all the other techniques failed. The technique used factors such as memory dumps, run-time traces, and output statements. Sometimes the efforts and time go waste.
Backtracking Technique
Backtracking is used for small programs. From the location of the problem, the source code is traversed backward to check for bugs. But for larger applications the backward paths becomes large.
Cause Elimination Technique–
Debugging is done by binary partitioning. A “cause hypothesis” is devised. Tests are conducted to eliminate the list of all possible causes.
Automated debugging –
The debugging approaches are supplemented with debugging tools. IDEs are provided to capture language specific predetermined e
ors without necessary compilation. Other debugging tools are tracers, test case generators, and mapping tools.
The e
ors were modified and an accurate product is obtained as discussed below:
Van Vleck [Van89] proposes three simple questions for removing the bugs:
1. Whether the bug cause is appears in another portion of the program?
Problem arises due to complex logic that can be reproduced elsewhere.
2. what will be the “next bug” that is introduced because of the fix I made? Before the elimination of the e
or, the source code should be checked for coupling of logic and data structures.
3. What should be done to prevent this bug in the first attempt?
If this is done the bugs can be eliminated from all future programs.
II. Dijkstra asserts that “Program testing can be used to show the presence of bugs, but never to show their absence!” Explain this statement.
According to Dijkstra, Program Testing is done to find maximum number of e
ors. The main goal of testing is to spot the e
ors in the program. Testing is done to find the bugs in the program. A good testing reveals most of the bugs. Once all the bugs are listed for the software...