Answer Posted / ravinder
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 ? | 3 Yes | 1 No |
Post New Answer View All Answers
Explain inputs?
What are enter & exit criterias of a test paln?
Which is not a tool of static code analysis? a.)Ada b.)Borland-delphi c.)Fortan d.)None
How many test cases will be there for testing the numbers of range -10.0 to 10.0? How it is classifying?
What determines the level of risk?
Explain defect?
Why we need localization testing?
How much testing is enough?
What is eexception?
Iam searching for job on testing with 2+ experience any sites are there for testing jobs and any reference forward mee....mail.id: rakeshreddi50@gmail.com
please anyone can help me in giving dumps in ISTQB for foundation level
Have you performed tests on the front-end and the back-end?
What is random/monkey testing? When is it used?
Explain what the meaning of code walk through is?
What is your primary role in your project?