2016 has been an eventful year in many ways. Some predictions came true such as the growth in number of online shoppers throughout the Black Friday madness, other events have been less predictable with Trump’s success in the US Presidential Election and the outcome of the Brexit vote in the UK.
One thing that each of these events did have in common though was that they all caused websites to crash.
In the UK when the deadline for voter registration for the EU Referendum was nearing, the application crashed due to unprecedented traffic. As Trump started to take the lead in key states in the US election it was reported that Canada’s main immigration website appeared to suffer ‘repeated outages’, and Macy’s, Argos and Quidco became victims of Black Friday traffic.
So what key steps can we take to ensure that we are set up to test applications and websites for success in 2017?
Software Development Life Cycle – Start Testing Earlier
With the adoption of different models of working such as agile, continuous development and test driven development, the role and order in which testing is taking place is changing. Doing testing early in the development life cycle enables defects to be captured in the requirements or design phases. Smaller updates to fix bugs can then be made early in development rather than later down the line when making changes to the full functionality of a large system can prove costly.
Software Testing Life Cycle – Identify risk and prioritise to keep focussed
As with everything the speed at which testing is happening is vastly increasing and when accelerated timescales come into play it is crucial that projects are structured to deliver from the outset. Regardless of the testing approach the requirements analysis is an essential stage as it will identify priorities and associated risks, which in turn will inform the critical elements that are at risk from bugs. Testing teams can then identify the key test cases to focus on and maximise their testing time.
Remember the 7 principles of software testing
Principle 1 Testing shows presence of defects
Principle 2 Exhaustive testing is impossible
Principle 3 Early Testing
Principle 4 Defect Clustering
Principle 5 Pesticide Paradox
Principle 6 Testing is context dependent
Principle 7 Absence of errors – fallacy
Try before you buy, sign up for a free trial of JAR:TestLab to load and functionality test your application.