Manual Testing

Last Updated on October 28, 2024 by Neil Murray

Manual Testing – Sections

  • UI Areas – what user sees in an area before taking any user action
  • Actions – changes that happen when user takes action in the UI
  • Testing Sequences – follow these sequences to test changes & releases
  • Logic – testing CF7 Skins Logic (both Backend & Frontend)
  • Testing Forms – CF7 Skins forms used to help with testing
  • Front End Forms – how CF7 Skins forms display on WordPress website
  • Responsive Styling – WP Backend/Admin at different screen sizes

Manual Testing System #

We need to test & confirm that changes made in each plugin release do not inadvertently affect the operation on all our the CF7 Skins plugins.

Key is to run testing in a standard format when we want to check a change.

We need a system:

  • Where we find problems instead of customers
  • That does detailed manual testing over a defined range of setups for PHP, WP, CF7 & CF7 Skins
  • Which confirms the plugins are working as they did previously before any change.

Aim is to:

  • record how each version is working
  • find unknown errors
  • get developers check key areas before each plugin releae
  • get developers to update this when we make changes

Further reading:

NOTES #

Need to also test with only specific plugins activated.

Save all Images to Sync – use ..\ Sync\..\Testing\Test Site\Manual Testing\