RE: how can we write testcases from Requirements..?
it is true that when ever we speak about the testing we say that testing strats from the reqiurment analysis so we should able to write the test case for the reqirement say ur developing a appliacation for whidh is developed for the accuontig then we are see that all reqirment that s/w taken or not file:///usr/share/doc/HTML/index.htmlfile:///usr/share/doc/HTML/index.html
RE: how can we write testcases from Requirements..?
Yes Requirements should represent exact functionality of AUT.
First of all you have to analyse the requirement very throughly in terms of functionality. Then you have to think about suitable testcase design techniques (Black Box design techniques like Equivalance Partitioning Boundry Value Analysis Error Guessing and Cause Effect Graphing) for writing the testcase.
By these concepts you should write a testcase which should have the capability of finding the absence of defects.
RE: how can we write testcases from Requirements..?
To answer the question of how to write a test case for a simple window.
Try to identify the text boxes and commands of the window then test for boundry text type of field (like password would be different than a regular field).
Then test the buttons and the functionality you would expect to happen after clicking that (like: if you click OK on a login window behind the screen a validation will happen and if the user and password are correct you would be granted a successfull entry etc....)
Try also to validate what happens when you click on the cancel button.
RE: how can we write testcases from Requirements..?
AUT is Application Under Test.
Yes we start writing test cases from the Requirements of the application.Once the use cases are designed we can identify the different test scenarios and write test cases for those scenarios.
