First thing I’d do is to understand the functional requirement of the page. Please note that it’s ok if you don’t have the requirement document but it’s hard to test if you don’t understand the requirement of system under test (in this case, a web page). Basically, I may want to figure out and validate the following:
* What is this page is about?
* What is it used for?
* Who is its user?
* What are the important feature of the page (for the user)
* Do they have competitor? Can it compare to its competitor?
* Responsiveness on Mobile, Desktop and its web browser
Depends on the business of the site, you may want to validate the performance or security
Hi Ana,
It’s a very good question.
First thing I’d do is to understand the functional requirement of the page. Please note that it’s ok if you don’t have the requirement document but it’s hard to test if you don’t understand the requirement of system under test (in this case, a web page). Basically, I may want to figure out and validate the following:
* What is this page is about?
* What is it used for?
* Who is its user?
* What are the important feature of the page (for the user)
* Do they have competitor? Can it compare to its competitor?
* Responsiveness on Mobile, Desktop and its web browser
Depends on the business of the site, you may want to validate the performance or security
For exploratory testing, I do recommend you read this post. It’s a great guiding start to testing without document (http://www.developsense.com/articles/2005-01-TestingWithoutAMap.pdf)
Cheers,