Thread: difference between test cases,test scenario,and test suite?

Hi friends
i want to take the example of the bus riding for expalining tht
test scenario:
some real time situations or work flow or real existence of work tht how we going to do tht thing. e.g:- we decided to go some whr by bus.so as we planed tht we wil take the bus from tht stop & reach tht palace.

test case:
" documented steps written 2 execute particular functionality of the component of software tht might contail expected results, inputs to ensure tht the desired functionality works fine."

e.g:-
1. First we take the riksaw from home.
2.reach bus station by riksaw.
3.take seat in bus.
4.reach there by bus.
5.left the bus after reaching to that place. & like that "these might b the some test cases tht u can think based on the above scenario"
hope tht u got the concept
if u find me wrong somwhere please notify me
i wil b thank ful to u
regards
rajeev sharma

Test case : Verifying the functionality

Test scenario : Set of Test cases.

Meaning of V Model in Project based companies.

Test Scenario is a big picture. There can be several test cases that can be written to test one test scenario.
e.g. Test Scenario - Test the checking account functionality for a bank application
Test cases for the same could be - Test checking form, test for required fields on the form, test for accuracy of the deposit/withdraw function, test for error conditions such as trying to withdraw more than available balance etc.,

Hope this helps

Hi srkishoredrdo,


I have collected few information on your query,some of your queries are already discussed in geekinterview anyway have a glance.

1) Thread testing

this link directs you to geekinterview specific discussion about thread testing http://www.geekinterview.com/question_details/32901

2) bucket testing

similarly this topic is discussed already,below link will provide you inforamtion http://www.geekinterview.com/question_details/28841

3) implementation testing

Implementation testing or sometimes called installation testing is typically completed by the software testing engineer in conjunction with the configuration manager. Implementation testing is usually defined as testing which takes place using the compile version of code into the testing environment or pre-production environment which may or may not make it into production.

This generally takes place outside of the development environment to limit code corruption from other future releases which may reside on the development environment. While the ideal installation might simply appear to be to run an install program sometimes called package software. This package software typically uses a setup program which acts as a multi configuration wrapper, which may allow the software to be installed on a variety of machine and/or operating environments. Every possible configuration should require extensive testing before it can be used with confidence.

In distributed systems, particularly where software is to be released into an already live target environment (such as an operational web site) installation (or software deployment as it is sometimes called) can involve database schema changes as well as the installation of new software. Deployment plans in such circumstances may include back-out procedures whose use is intended to roll the target environment back in the event that the deployment is unsuccessful.

Ideally, the deployment plan itself should be tested in an environment that is a replica of the live environment. A factor that can increase the organizational requirements of such an exercise is the need to synchronize the data in the test deployment environment with that in the live environment with minimum disruption to live operation. This type of implementation may include testing of the processes which take place during the installation or upgrade of a multi tear application.

This type of testing is commonly compared to a dress rehearsal or may even be called a “dry run”. Implementation testing is testing of a full, partial or upgrades install/uninstall processes.

Ref: http://en.wikipedia.org/wiki/Installation_testing

hope it helped you.

Regards, sridevi

Test case is a condition which confirm that actual result is same as the expected result.

Test scenario is use case condition , how user can use the system.