I would personally talk to my Business Analyst understand the functionality and refer the BRD documents that he or she prepared or prepare it myself and write Test Plan And Test Cases and execute them.
One thing I can tell you if there is no documentation that would be a very bad practise.
arvind
Sep 25th, 2006
if u dont hav any document then u hav to go for the adhoc approch or exploratory testing. note down the every steps and there outcome actual result, try to explore the software first once u understand the functionality of software than u can write test cases on that plz correct me if i m wrongregardsArvind
if we dont have proper requirements then we have to see the screens once thoroughly and based on our previous project knowledge we will prepare test cases and also we are getting knowledge transfer from dev team and then we will write test cases
If we don't have proper requirement documents then we will follow adhoc testing depending on the previous experience to test the entire functionality of the application.
If there are no requirement documents to reference, then you can still create test cases:
BEFORE THE PRODUCT IS RELEASED TO TEST
Learn as much as possible from expert and knowledgeable stakeholders about end-user (customer or client) requirements. You can begin authoring test cases based on this information. You may or may not have a Business Analyst on the project. If not, the Project Manager should be able to guide you in the right direction.
AFTER THE PRODUCT IS RELEASED TO TEST
Conduct exploratory testing and learn about the application while you author test cases.
If we do'nt have proper Requirement documents (No DOCS at tall) then how can we write test cases. Based on what...