Web Application: what are the steps to test a website or how to test a website
There are various ways and it's like question of what contains in Manual Testing.
According to me,
1. If the Application is not ready and 'in-progress' phase
- Tester can devide application in various modules where a particular major functionality is covered. We have Business Specification Documents, Functional Specification Documents with Workflow stated.
- Try to understand those and figure out how would the application look like as mentioned in the flow. There may be 'mock-ups' provided which would help in understanding the application
- Create scenarios using functional documents, then Create Test Cases. Get them reviewed from your senior.
- Once the execution is started, execute the test-cases. Have smoke testing to get to know that whatever picture you have created of your project is the same of something made different.
2. If the Application is ready
- Again have a smoke testing and understand the flow. Take particular module. and Start Testing.
Now testing includes functional testing, UI testing, Validations, Positive Scenarios and Negative scenarios.
If all modules are ready then it's System Testing, Intigration testing.
For UAT, End-to-End testing.
For Testing, you need to know which all possible scenarios can happen around the impacts created by modules in a various ways.
This all I can only write. Rest is upto tester on how deep he/she wants to break the code! :)
I am still not satisfied what I wrote here cause afterall it all depends upon testers thinking and ways he adopts...!!
We Hope this helps!
Thanks!
There are various ways and it's like question of what contains in Manual Testing.
According to me,
1. If the Application is not ready and 'in-progress' phase
- Tester can devide application in various modules where a particular major functionality is covered. We have Business Specification Documents, Functional Specification Documents with Workflow stated.
- Try to understand those and figure out how would the application look like as mentioned in the flow. There may be 'mock-ups' provided which would help in understanding the application
- Create scenarios using functional documents, then Create Test Cases. Get them reviewed from your senior.
- Once the execution is started, execute the test-cases. Have smoke testing to get to know that whatever picture you have created of your project is the same of something made different.
2. If the Application is ready
- Again have a smoke testing and understand the flow. Take particular module. and Start Testing.
Now testing includes functional testing, UI testing, Validations, Positive Scenarios and Negative scenarios.
If all modules are ready then it's System Testing, Intigration testing.
For UAT, End-to-End testing.
For Testing, you need to know which all possible scenarios can happen around the impacts created by modules in a various ways.
This all I can only write. Rest is upto tester on how deep he/she wants to break the code! :)
I am still not satisfied what I wrote here cause afterall it all depends upon testers thinking and ways he adopts...!!
We Hope this helps!
Thanks!
No comments:
Post a Comment