Testing Basics

call us now - 0845 757 3888
  • view dates / book course
  • course description
  • blogs

Print course outline | Download Word document | Link to page: http://www.qa.com/TPQ30010

Course dates

Currently scheduled dates for this training course
LocationJunJulAugSepview later dates
LocationOctNovDecJanview earlier dates
London
  1. Currently scheduled dates for this training course
    London, EC|-|-|-|27show prices/book
    LocationOctNovDecJanview earlier dates
    London, EC|-|28|-|-show prices/book
  2. London, EC

    hide-prices
    27 Sep £400 exc VATenquire about this course
    28 Nov £400 exc VATenquire about this course

Print course outline | Download Word document | Link to page: http://www.qa.com/TPQ30010

Overview

As a new tester, an individual needs to understand why we test software, what is software testing and some of the key terms & principles of software testing.
This course aims to address the key issues for a person who is new to software testing or who is going to be involved with software testing.

Prerequisites

There are no pre-requisites for this course.

Who should attend?

This course is suitable for anyone wishing to gain a basic understanding of software testing.

Delegates will learn how to

  • Be able to explain why we test software and the risks of not doing so
  • Be able to describe the benefits that structured, planned testing can provide to an organisation
  • Understand the software development life cycle, the points at which bugs can be introduced and how testing can help us identify bugs and even prevent bugs from occurring
  • Be able to describe the main steps in the fundamental test process
  • Understand the various levels and types of testing and how they can identify existing bugs and even prevent bugs
  • Understand key testing terminology

Course Outline.

The need for testing

Why do we need to test software and what happens if we don’t do it?
What is software testing?
The benefits of testing and when we should start testing for maximum efficiency
Why we can’t test everything
Testing and quality – two sides of the same coin?
Key testing terms – error, fault and failure
The software under test

How software is built – understanding the software development life cycle
Why are mistakes made during development and how can they be prevented?
The test process

Why planning is key to the success of a testing project
Defining the test objectives and when to stop testing
Estimating the task ahead
Prioritising and risk management and what part they play in the test process
Deciding what to test
Writing test cases
Running tests and recording the results
Monitoring the progress of testing
The different types and phases of testing
The test team – roles and responsibilities
What to test

Identifying the things we want to test and which will make the most difference to the testing project
Test cases – what are they?
Testing in different development environments

The V-Model
What is agile testing

Print course outline | Download Word document | Link to page: http://www.qa.com/TPQ30010

Related blogs

8 things you can do for Learning at Work Day 2013

Posted by Tony Martin on 21 May 2013

In case you didn’t know, since 1999 Campaign for Learning (CfL) has promoted an annual awareness day that supports learning in the workplace. This year it is Thursday 23 May and the theme is “Many ways to learn”.

Competent Project Managers – now there’s a thought!

Posted by Tony Martin on 08 February 2013

Having been in the Learning and Development industry for over 15 years I have seen many ‘silver bullets’ aimed at creating staff that are competent to do the job they were employed to do to drive organisational success. In fact, the quest for the elusive formula has been going on for a lot longer – in the project management profession there has been over 30 years of “the next best thing”.

A model is a powerful Business Analysis tool

Posted by Marie Bradley on 21 January 2013

How many times do you use models in your everyday life? Go on think about it…How did you get to work? If you used any form of map, including the tube map, then you used a model. If you asked a model for directions then yes you could argue that you used a model but really that would be missing the point…Although well done if you did that and then reached your destination!

Business Analysis? What’s that then?

Posted by Marie Bradley on 14 November 2012

Anyone who has ever worked as a Business Analyst will be familiar with this line of questioning and will likely approach any scenario that could prompt it with a certain amount of trepidation.

OWASP Top 10: #1 – Injection. How to prevent attack.

Posted by Phil Stirpe on 06 November 2012

This is one in a series of videos and blog posts that explore the top 10 most critical web application security risks as defined by OWASP.

See all related blogs

 
top of page
  • IIBA logo
  • bcs-partner logo
  • TOGAF logo