Thread: If test case required for testing always post test scenario.

YES :-)
It should be a specific scenario... Other wise it will not be in scope to give the answer like as said writing test cases for Banking Project, Phone, Elevator...etc queries :-)

I like this suggestion very much.
Questions for need of Test cases should come up with the Scenarios and some useful conditions, then only the people here can suggest / help the requester well with good and suitable test cases.

I strongly agree with jainbrijesh.

The test scenarios are tied to individual use cases. Each test scenario describes the specific test case that must be automated or doing by mannualy.

correct me if i'm wrong

HI my friend ..
i'm answering that question.

posting a specific scenario ,for which we need test cases,certainly does help in getting precise respones.it seems like a good idea,also saves everyone a lot of time.

i am sure brijesh agrees to that!!what abt others?

Yes certainly a test scenario is important, but is there any probability to try writing testcases siting examples?

This is indeed a good idea.. In the process of finding out the scenarios to post.. we might end up writing test cases by ourselves, as I believe that If we dig deep in ourselves, we can find most of the solutions!

Thx for the advice!

hi Kain,

i totally agree with your point

Thanks
Sushma

What types of testing do testers perform?
Why Should we prepare traceability matrix? is it necessary?
When should testing start in a project?
Explain the real time testing experence, that means how to test the application and how to find out bugs and how to submit bug report.


ok thanks
hanu

hi hanu,

i think what do you mentioned in thread is interview question. please start new thread while posting the question.

What types of testing do testers perform?
it hardly depends upon the application u use.

Why Should we prepare traceability matrix? is it necessary?
To track issue

When should testing start in a project?
As per my view once the design completes

Explain the real time testing experence, that means how to test the application and how to find out bugs and how to submit bug report.
start testing any sample site so that u can gain real time experience or else, what ever i communicate you will not be able to understand.

Thanks
Deepasree

I agree with Brijesh...

Regards,
Narin Kamuni

I agree with brijesh, this should be treated as a basic criteria, remember one thing, the bug or scenarios which can no be explained or re-produce the chances of getting fix for that also decreases. Request you all try to explain the scenarios and if possible then give some example, so that the person who is interested in providing solution will find it easy and you will also get the required solution.

Happy testing

Sarvesh

A test case may contain many scenarios e.g. testing of a login page a few scenarios would be as follows:
1. Right password, wrong user name
2. Right user name and wrong password
3. Right user name, no password
4. Right password, no user name...ect.

Depending on the complexity of an application/system, a test case may be 10 page long or 200 page long. For instance, if one were to test a simple application which was built to inventory other computer systems and applications of a company, systems' owners and departments and capture the systems' statuses then the test cases would be short. Each test case would be about 10 - 50 page long. Whereas, if one were to test a pre-clinical data acquisition and management system, a test case may be 200 page long.

I would differ with the notion of a test scenario contains many test cases. Each test case is written to test against a requirement or requirements and each scenario involves 1 or more requirements. Each test case contains many test steps in numerical order and each scenario may contains 1 or more test step(s).

The terms 'test case' and 'test script' are used interchangeably. Following GAMP 5, some organizations customize their SDLC to have System Test Protocol which strategizes on how one approach to test the sytem. This means a System Test Protocol contains many System Test Scripts. Each test script is written to test one or many requirements.

I hope this helps and would love to hear from you guys.

Completely agreed with Brijesh. Any member who is looking for answers to a specific subject must explain the actual problem he/she is facing. It will others to understand the topic and they can expect answers to the point.