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

Test cases are written for test scenario

and test scenario is a big picture

is that right..if i am wrong please correct me
thanx

jay

Dear All,

Could you send me the interview point of QTP questions?

Regards
Rishi

hi friends

the answer is very easy

based upon the SRS requirements only we are preparing test scenario

BAsed on test scenario we are preparing test cases

Test scenario is nothing but checking what are all the probable test conditions we can make for that particular requirement

Test case is derived based on test scenario whether it may be positive ar negative

regards

saravanan

Hi i would like to know what are the Main questions have been asked during the Interview,I am A softwre tester

Hi ... can anyone tell me that which software are commonly used by MNC for generating bugs reports. Please it is very necessary
Thanks......

Hi can You guys update me on the functional testing interview questions please

Can u explain about Test scenario breifly?

Test scenario:i can say that it is an area(or situation) where we have the scope to perform testing.

Test case: it is an idea of test engineer , it tells how the testing can be done in that particular area or situation of the application

Test suite: it is the combination of diff. types of test cases.
scenario-->test case-->test suite.

Test Scenario :- sequence of action to execute test case

Test Case : A set of input values,precondition ,expected result prepared in some document.

Test Suite : it is set of several test cases where the post condition of one test case is used as precondition of another test case

This discussion really helped me.. getting a clear picture

Thanks guys

Hi Kishore,

I have tried to answer your question, and hope this will help you

1.What is thread testing.
Ans:- A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.

2.What is bucket testing and which automated tool is used to do this test.
Ans:-
Bucket Testing" (also known as A/B Testing) is mostly used to study the impact of various product designs in website metrics, two simultaneous versions were run in a single or set of web pages to measure the difference in click rates, interface and traffic

A/B testing or bucket testing is a method of marketing testing by which a baseline control sample is compared to a variety of single-variable test samples in order to improve response rates. A classic direct mail tactic, this method has been recently adopted within the interactive space to test tactics such as banner ads, emails and landing pages.

Significant improvements can be seen through testing elements like copy text, layouts, images and colors. However, not all elements produce the same improvements, and by looking at the results from different tests, it is possible to identify those elements that consistently tend to produce the greatest improvements.




3. ERP testin automation testing.

Ans:-
There are a variety of testing processes implemented in a standard testing schedule.
At the first level is performance testing
Tests an ERP solution for whether it can handle the kind of loads being placed on the system by simultaneous users or high amounts of data or transactions.

The ease and efficacy of performance testing is dependant on the quality of the testing plan, testing tool, people on the testing team and the quality of performance data capture. One important tip to remember in performance testing is that it isn’t always necessary to try to test the worst case since testing tools can always generate far more transactions than is possible by human operators.

Another key testing process is functional testing, where all system features or functions, both software and hardware are tested to ensure that the ERP solution conforms to specifications and meets requirements. Successful functional testing is entirely a matter of proper definition: the specific definition of test goals will determine the appropriate functional tests required, from data mapping to business process tests to access control systems to regression testing.

Further important steps in the process include documenting key business processes, developing modular test components, setting up a test lab, executing regression testing and analyzing defects and creating test reports.

While performance testing and functional testing form necessary, basic building blocks to ERP testing, the meat of the process lies in integration testing. As much as an ERP solution is tuned and adapted to an organization, it is never a perfect fit, and requires some adjustments in people and processes as well. Thus, the most crucial aspect of testing is not the functionality of a package (as such quality is assured to some extent with a premium solution), but rather the implementation of the package into the organization. The question thus, is not whether the solution provides all the necessary features, but rather how well the combination of customization and changes in the organization’s processes meet the requirement for which ERP is deployed. Integration testing should be approached from a process-oriented perspective, and should involve the performance of actual business transactions featuring employees that will finally perform those transactions rather than simply pushing dummy data from system to system.


4.What is Data Warehousing testing?
Ans:-
Data where house is Subject oriented,Integrated,Time-varient and non Volatile. It contains the data for management's decision support system.

Testing for a Data warehouse consists of requirements testing, unit testing, integration testing and At the end UAT, the system should be acceptable to the client for use in terms of ETL process integrity and business functionality and reporting.



5.What is Implementation testing?
Ans:-
Implementation testing generally refers to the process of testing implementations of technology specifications. This process serves the dual purpose of verifying that the specification is implementable in practice, and that implementations conform to the specification. This process helps to improve the quality and interoperability of implementations.


6.What is Shake out testing?
Ans:-To identify an initial test which verifies that a load has been successful and all software is accessible and functioning as expected. This is also to test the Networking functionality, Data base connectivity and the integration of modules.
This is mainly carried out by developer.


Thanks
Sarvesh

In one sentence we can say that Test Scenario is something related to a complete scenario in which many more possible options are present but test case is all that individual possible option over there.

Like Scenario is Login into an account.
Test cases consists of
a. Empty user name, empty password.
b. Empty user name with a correct login password of any account.
c. A correct User name with Empty Password.
d. A Correct User name with wrong password.
e. Wrong user name with any existing account's password.
f. Wrong user name and password combination (i.e. both user name and password exist but not mapped with each other)
g. Correct user name with correct Password

In a simple way to define both:

Test Scenario: A general version of test cases. It helps team to actually get the basics of how to use the system. Its more interactive between the actors and system. For example: Login to System A, Create users in a company etc. If you see these are very general terms to define the functionality of the system.

Test Cases: These are the same thing but into more details providing specific steps to define the test scenario. The same above examples in terms of test cases may be defined as:

step 1: Open a browser
Step 2: When you get into login page, login using these user accounts
step3: save the user

Expected results: the user must be successfully logged in if he had provided the valid user account.

Originally Posted by vennela

hi one and all
this is vennela

Hi everyone.
this is chandu.



can u explain use case and test case with examples pleaseee

Test case: testcase means simply excepted and excuted results
Test senerio: at which cases you are testing a condition like no.of permitation and combination
Test Suite: collection of test cases..

Hi everybody,
I'm new to testing and this forum as well. Pl guide me how to write test cases on mercury flight reservation system.