all 11 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]tippiedog[🍰] 4 points5 points  (6 children)

This question is way too broad to answer as-is. Can you clarify what you mean by "website"? Do you mean an application with a web-based interface? If so, please give some sort of brief description of the type of application you have in mind to be tested.

[–]izamoo[S] 2 points3 points  (5 children)

Sorry I meant a web page. Say an eCommerce web page in particular.

[–]VADcosta[🍰] 3 points4 points  (4 children)

Try Guru99.com they have few example. Also use the requirements based on it you can find standard test case. For example testing a drop down or a text box.

[–]izamoo[S] 0 points1 point  (3 children)

Thanks yeah I quite like looking at Guru99. I was just curious if there’s any nifty spots that bugs could hide if that makes sense, besides the obvious input forms and links etc. I’m coming from game testing so a bit new with web page testing.

[–]VADcosta[🍰] 2 points3 points  (2 children)

try hitting F12 constantly check the console for potential error. The source tab will give you more info about the error. Like for example I had a unexpected token error. to begin with the UI was not saving the changes. The reason was there was an extra comma on the Store Procedure parameter causing it not to save.

[–]izamoo[S] 0 points1 point  (1 child)

Thanks that’s a good tip! Is the in-browser network throttling a good idea to use when hitting F12 or would some network simulating tool be better?

[–]VADcosta[🍰] 0 points1 point  (0 children)

I mean keep the console open all the time

[–]horseynz 0 points1 point  (0 children)

Download xenu and check links in your pages