This is a 4 day course - shorter days to allow more time for revision or getting back to the day job.

Courses run from 9am to 3pm, 2pm finish on final day.

Day 1 - Theory Day (K1 - K2) – 9am – 3pm

• Fundamentals of testing - this includes principles of testing and the test process, both of which set up your underpinning knowledge and understanding, not just for your assessments, but for managing testing in your future career.
• We practise exam style questions.
• As homework you revise the day's learning and practise more exam style questions.

Day 2 - Theory Day with a little techniques added (K1 – K3) – 9am – 3pm

• Software development lifecycles - here we put the V and iterative models in context in today's world. This learning complements the testing fundamentals to provide the understanding of how testing fits into the overall project. 
• We practise exam style questions.
• Static testing techniques - here we show why it is still important to review requirements and user stories before expending energy on cutting any code. Whilst this may seem obvious, the nature of software development can mean that we run too fast and fail too late. To address this, we show why we should 'shift left'.
• We practise exam style questions.
• As homework you revise the day's learning and practise more exam style questions

Day 3 - Techniques Day (K1 - K3) – 9am – 3pm

• Dynamic testing techniques - here we show the value of designing tests, including the valuable traceability that this affords when bugs escape into the next stage of development, despite your best efforts. We cover black-box; white-box and experienced-based test design techniques. We practise exam style questions.
• As homework you revise the day's learning and practise more exam style questions.

Day 4 - Final Theory Day (K1 - K3) – 9am – 2pm

• Test Management - we wrap up the course with a look ahead to how you may manage projects in the future.  We discuss the value of independent testing, even in cross-functional teams.  We provide a reminder of the necessity of considering risk at all times whilst testing.  For those yet to raise a bug, we take a look at a key deliverable from any test effort - to highlight potential problems in software and the associated risk with not addressing them. We practise exam style questions.
• Test Tools - this is a very brief look at how the testing process may be supported through the use of automation in testing. We practise exam style questions.
• Final exam preparation - you will be provided with a full sample paper and exam revision tips.  We remain in contact until exam day, so that you have a familiar port of call for any questions or concerns.