A human mind is incapable of memorizing every single piece of information that it receives thus we’ve invented pen, paper, a red rubber around the wrist, etc. Testing is in no way different, so here is an example of a not-to-forget list you may use when performing desktop testing.
First let’s divide the list into levels. The first one would be GUI, the User Interface Testing.
What to do on this stage?
- Correct the content and the words used in the web page
- The wrap-around needs to flow smoothly
- Check the app’s instructions. They have to be precise.
- Are your pictures displayed accordingly with text? Double-check that.
So we are now going for the most time and effort consuming part – the functional testing.
- Watch out for broken links. Eliminate them for good.
- How you’re warning are messages doing? Are they being displayed in a proper business-oriented way?
- Resolutions have a huge impact on the app’s performance. Make sure your project is responding properly to various resolution changes.
- Verify the next print relating things: watch how it behaves when the printer is both connected and unattached; test the prints functionality; check whether the app is giving an error message when the printer is broken or has no paper, etc.; double check the print layout of rather long event descriptions, etc.
- Make sure your app is doing great after the user has changed its theme
- Make sure the app installation process in flowing accordingly, whether the app is installed to the right folders, gets removed easy and properly and older versions can’t be installed over newer ones.
- Create a few user accounts with various access and enjoy playing with your app. Is it doing OK with every user? Check if the app is launching properly in a new user account, switch between them and watch how it is handling itself when two or more users are using the same account.
- The sleepy tests. Put the system to sleep, while your app is running, then in a couple of minutes verify if the app is still running and whether there are no errors or distortions
- Check if the app is running fine after you delete its cache both when the app was running and not.
And we’re almost through and getting to our step three the compatibility testing.
- Test the app on various OS of your choice and demand due to the fact that not everything can work with same shine in different systems
And the final stage: performance testing.
- Watch out for downtime. Check if everything can be functioning properly for a very long period of time.
- Check for the usual memory available in the comments columns.
- Run the powercfg/energy command. Thus you will be able to generate the report about power efficiency and it’s diagnostics.
Now we have a pretty good testing plan for our favorite desktop app.