Software Testing - end to end testing

Author

end to end testing

anand4180

2007-03-17, 4:23 am

when doing end to end testing wheather we stop the testing and
contact some other testing?

Phlip

2007-03-17, 4:23 am

anand4180 wrote:

> when doing end to end testing wheather we stop the testing and
> contact some other testing?

You never stop testing. You "analyze" (meaning "guess") how much of each
kind to do, and then you release whenever the program passes all tests and
has new features.

And most of your tests should be automated. Again, you "analyze" to discover
how many.

--
Phlip
[url]http://www.greencheese.us/Z

Land[/url] <-- NOT a blog!!!

Vladimir Trushkin

2007-03-20, 7:19 pm

On Mar 17, 6:13 am, "anand4180" <anand...@gmail.com> wrote:
> when doing end to end testing wheather we stop the testing and
> contact some other testing?

I hope I understood your question correctly and you are asking about
when one end-to-end test ends and another begins. This is not a
trivial question. I prefer to look at the end-to-end testing as the
modeling of real user behavior. In order to build an effective end-to-
end test one needs to look at the system functions in a whole.

For example, if you are testing a text editor try the following
sequences for end-to-end testing:

1. Create new file -> Write text -> Change some text -> Save -> Change
some text -> Print -> Close the file -> Verify changes.
2. Open existing file -> change some text -> save changes -> open
another existing file -> find and replace -> print -> save -> close.

Usually all these operation can be tested thoroughly using small test
cases. End-to-end might just give additional confidence that there are
no alternations in the operations caused by other operations, no
implicit dependencies between functions.

----
Best Wishes,
Vladimir

Sponsored Links