Do they actually use their own product? That’s my main question when I can’t use an application. Many devs, seniors etc… don’t seem to understand this but when I see a stupid bug, I put that app in the “suspicious” list (aka I don’t give my money). So… you, yes you, my little tester, it’s the time to step up and be ignored! Functionality testing is the basic and the most important step. That’s why it’s in step 1 (Duh!).
Links and forms. Yes I know, this is basically the entire website but this is not entirely true. This is the front-end functionality testing.
Next step is the “behind the FE” thingies. Cookies and database. I don’t want to auto-logout while I’m browsing and when I submit something, I want to store them. Got it?
Use it! Use your product. Navigate, use the pagination, check the content and your galleries. It’s the right time to get out the psychopath you keep in you. Check your product and you have to be sure that it’s easy to use for all ages and all levels. Clear options and clear instructions.
By “interface” we don’t mean the design. We are not talking about “compatibility” (next step) testing. As interface, we call the point where the server and the app/application meet each other and interact. Simpler: interaction between web server and application. At this point, you got to test all the possible failure scenarios. Especially the part where the customer gets an error. Is the error translated correctly or he gets something like “Emsg cf23df2207d99a74fbe169 :: Token e3eba035e633b65d94”.
Browsers, mobiles, tablets, operating systems, and printing. I am going to completely ignore the last part because…. I can. Do I really have to tell you what to do at this point? Just a tip: talk with the system administrators and ask them to give you a list of the most common (top 10 maybe) devices, browsers and operating systems that your customers are using. Nevertheless, you have to test on all devices, browsers, and OS.
As a professional (yawn) I have to say (yawn) this (yawn): “We separate, performance testing, in two sections. Stress and load testing.” (Yawn). The idea is to push your product to its limits. The thing is that there are tools available that can do this for you but (I dare you. I double dare you tester) to ask your superiors to do that. You can’t actually test many things on this step. Use a few forms simultaneously, multiple tabs and of course test your product with a slow connection (Chrome -> Developer tools -> Network).
I have to build a form => Build form => QA => Block. This is the part which (at first) a developer ignores. Change the ID from a page, paste an internal URL without being logged in, use symbols and scripts in forms etc. The most common is that you can run scripts by submitting a form and they never never never use trim in their user/pass fields. Last part? Check if the SSL is available everywhere and if not, show the proper message to the user. And by the way, you should ask them to log any security breach attempt. Yes, you! Step up and be ignored!