Answer Posted / b singh
A back end is the engine of any client/server system. If
the back end malfunctions, it may cause system deadlock,
data corruption, data loss and bad performance. Many front
ends log on to a single SQL server. A bug in a back end may
put serious impact on the whole system. Too many bugs in a
back end will cost tremendous resources to find and fix
bugs and delay the system developments.
It is very likely that many tests in a front end only hit a
small portion of a back end. Many bugs in a back end cannot
be easily discovered without direct testing.
Back end testing has several advantages: The back end is no
longer a "black box" to testers. Many bugs can be
effectively found and fixed in the early development stage.
Take Forecast LRS as an example; the number of bugs in a
back end was more than 30% of total number of bugs in the
project. When back end bugs are fixed, the system quality
is dramatically increased.
| Is This Answer Correct ? | 42 Yes | 3 No |
Post New Answer View All Answers
What is operational requirements?
Suggest some good webinars on Testing concepts?
What's Stress Testing?
What is fault masking explain with example?
Which one you prefer, working with independent testing project or working along with development team?
How do the companies expect the defect reporting to be communicated by the tester to the development team. Can the excel sheet template be used for defect reporting. If so what are the common fields that are to be included who assigns the priority and severity of the defect.
What is 2 tier and 3 tier application? Pls illustrate it with appropriate example.
Explain installation testing?
What is crash?
What goes into a Test Summary? How would you write a Test Summary?
26). how will know do written test cases are sufficient to validate application of functionality? 27). how will you prepare test data to validate input object? 28). explain defect status? 29). how will know whether the developer accepted you defects or not? 30). explain acceptance test? 31). explain when we stop testing? 32). explain scope of your project? 33). in which module you conducted testing? 34). explain defects which you found in that module? 35). if defect is not reproducible then what information you will provide to developer 36). if developer is not accepted your defect then what you will do?
What is a database administrator?
What the meaning of breath testing is?
Hi All!!Can anyone please suggest some better website to learn Mainframe Testing??Am very much new to Mainframes. Thanks in Advance Nithya
Explain what test deliverables is?