The current trajectory of software delivery patterns suggests there are very few instances where the methodology of choice is a single linear/serial journey through the testing lifecycle.
It is more realistic that best practice is a structured set of activities which individually and collectively will consist of one or more iterations.
The 'Key Activities' listed on this page represent a templated set which should form the basis for testing on any software delivery project; project needs would determine the extent to which each activity is applied.
Splitting the software testing cycle into these discrete areas should help realise benefits that are listed (but not limited to) the following:
User Interface (UI) design is central to the user experience and tools that promote design best practices provide an entry point for setting expectations for UI behaviours. Watch the M3 video for more ...
