How to prepare test cases using a prototype and how it contributes to testing activity?

1. Have you prepared of test cases using a prototype within the context of a formal development. Describes an approach to building a prototype using an example

2. Discusses how a prototype contributes to the testing activity as part of a lifecycle based on the use of formal methods

Questions by lravi4u   answers by lravi4u

Showing Answers 1 - 9 of 9 Answers

Test cases can be prepared using prototype which might include baselined SRS and Visios/TSD/WFD/Mock Ups of the project. One has to write test cases based on the requirements stated in the SRS and also depending upon the screens shown in the visio documents (whichever is there). Rest one can consult with the Analyst of the project who has got stated requirements from the client, can clarify the doubts if any.

The test cases are made to run when the project actually comes for testing. So one can have understanding of the application by going through the test cases. Testing is done by executing the test cases.

1. Have you prepared of test cases using a prototype within the context of a formal development. Describes an approach to building a prototype using an example

 Ans: I think in most of the comps everybody prepared the test cases based on proto types, now a days all are given the prototypes, by doing a brief review on requirements we can get some idea as how the application is going to be work, so based on our assumption we can write the casesm and i feel it's entirely creativity to write the cases by seeing the proto type.

2. Discusses how a prototype contributes to the testing activity as part of a lifecycle based on the use of formal methods.

  Ans: Yes it's definitely a good contribution to QA by providing the prototype, instead of writting cases by seeing the requirements (SRS), it's good to write the cases by seeing the Prototype if provided.


Srinivas

  Was this answer useful?  Yes

Prototype is one of the SDLC model. Actually prototype means it a model software developed with basic requirements to know how it works, with this basic only the developers will make the project to a extent of some more higher things while in the prototype itself we know that what is the major bug will arise at that time itself we know in which area we have to concentrate on more. If the project is developed from prototype then we can know easily that if it made to higher extent in which area we have to make the testing high i.e area of complication.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions