--
You received this message because you are subscribed to the Google Groups "MS2 CGA Winter 2012 Study Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ms2-cga-winter-2012-s...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Sent from my BlackBerry device on the Rogers Wireless Network
--
--
--
Stanley:
In my opinion, system testing & stress testing are totally 2 different tasks.
Some differences:
1. System testing is part of program testing, whereas stress testing is part of acceptance testing.(Note that program testing does not consider user interaction/requirements, whereas acceptance testing considers user acceptance/needs.
2. System testing is straight-forward whereas stress testing wants a tester to think like a thief trying to make problems in the systems. What happens if you don’t follow a procedure.
Conclusion:
Systems testing & Stress testing are very different.
Analogy:
Lets consider a purchasing cycle (Pending PO report)
Systems testing will test if new system will generate a pending PO report. If report is produced, everthing is fine n dandy.
Now stress testing will test as to what happens if the AP clerk enters a particular invoice without clearing a PO for the said invoice. Remedial measures in this case might include cross-referencing Item codes on PO’s & Invoices within a 5-day time-frame.
Testing hierarchy is as follows:
Testing(Software)<1)Program testing <2) Acceptance testing(User-focused)
1.a).Unit testing 2.a).Recovery testing
1.b)Integration testing 2.b) Security testing
1.c) System testing 2.c)Stress testing
2.d)Performance testing
I hope this clears your concepts.
Regards,
Amanpreet Sidhu
From: ms2-cga-winter-...@googlegroups.com [mailto:ms2-cga-winter-...@googlegroups.com] On Behalf Of Stanley D'Souza
Sent: March-01-13 7:18 PM
To: ms2-cga-winter-...@googlegroups.com
Subject: Re: Hi All
Hi guys,