What is the approach that should be followed for manual testing?

Please help me by providing your views.

Thanks

Gokulakrishnan K

hi,

can you please be clear with your question, i think its me who didnt get you right??

Thanks
Sushma

hi friend..


Approach as per my understanding are you asking about the SDLC or STLC.. Tell me precisely.. I will help you out

Thanks
Deepasree

Deepasree/Sushma

Are we follow Top Down or Bottom Up approach for Manual Testing.

If any one of this, then pls give example for each one.

I think that I made it clear.

Thanks

Gokulakrishnan K

Given the following fragment of code, how many tests are required for 100% decision coverage?

if width > length then
biggest_dimension = width
if height > width then
biggest_dimension = height
end_if
else
biggest_dimension = length
if height > length then
biggest_dimension = height
end_if
end_if

Please let me know the answer as well the method to calculate

Thanks

Gokulakrishnan K

Hi friend..

Top down approach what is top down approach? top down approach is to start implementing presentation layer and then implement the business logic.

Advantage: • easy to visualize functionality. • sense of completeness in the requirement. • easy to show the progress of development.

Disadvantage: • ui driven approach hence high possibility of redundant business logics. • since an ui is readily available no developer would write a unit test cases. • no concrete layer to rely on, as both presentation & business logic keep evolving. • lack of concrete test suits to ensure one layer is tied up.

Bottom up approach what is bottom up approach? bottom up approach is to start with the concrete business logic and its testcase and proceed with presentation implementation.

Advantage: • solid business logic, hence zero redundancy • good unit test case can be written to validate changes. • developer has only option to use unit testing tools to test the logic. • easy to manage changes and modification.

Disadvantage: • effort involved to write test cases. • progress of implementation cannot be show very effectively.

Thanks
deepasree

hi friend,

Both the approaches have advantages and disadvantages

Bottom-up approach:An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

Top-down approach:An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested

i have attached a file for your reference.

Attached Files

Approach.doc (136.5 KB, 20 views)

Deepasree/Sushma,

I sincerely thank you for the details provided by both of you.

Thanks

Gokulakrishnan K

hi,

Happy to help at anytime

Thank
Sushma

hi

When the end user finds a deviation from expected speific or expected result, what is it called as??. i mean do you call it as defect or failure. Any information would be much appreciated.

Thanks
Sushma

hi friend

The software faults occur through the following process. A programmer makes an error (mistake), which results in a defect (fault, bug) in the software source code. If this defect is executed, in certain situations the system will produce wrong results, causing a failure.[4] Not all defects will necessarily result in failures. For example, defects in dead code will never result in failures. A defect can turn into a failure when the environment is changed. Examples of these changes in environment include the software being run on a new hardware platform, alterations in source data or interacting with different software.[4] A single defect may result in a wide range of failure symptoms.

Not all software defects are caused by coding errors. One common source of expensive defects is caused by requirements gaps, e.g., unrecognized requirements, that result in errors of omission by the program designer. A common source of requirements gaps is non-functional requirements such as testability, maintainability, usability, performance, and security.

Bug
A software bug (or just “bug”) is an error, flaw, mistake, failure, fault or “undocumented feature” in a computer program that prevents it from behaving as intended (e.g., producing an incorrect result). Most bugs arise from mistakes and errors made by people in either a program's source code or its design, and a few are caused by compilers producing incorrect code.

Thanks
Deepasree

hi friend

Error : It is the Deviation from actual and the expected value.

Bug : It is found in the development environment before the product is shipped to the respective customer.

Defect : It is found in the product itself after it is shipped to the respective customer.

Thanks
Deepasree

hi deepasree,

i got a clear idea but just want to confirm that , if the end user find any issue, is it called as failure or defect

Thanks
Sushma

hi friend..

As per my view it is defect

Thanks
Deepasree

hi deepasree,

Thanks for the confirmation, i was really confused, because i was going through one of the ISTQB examination papers and they have given answer as "failure" so thought of just posting it in the forum. Thanks for your time

Thanks
Sushma

hi friend..

if you have any other doubts too please post it in the forum.. i will help you as much as i can

Thanks
Deepasree

Thanks a lot deepasree

Thanks
Sushma

hi,

Can anyone explain me what is meant by Error Guessing in testing

Thanks
Sushma