The Fundamentals of Software Testing - Part 1


What is The Fundamentals of Software Testing? - Part 1


 
“The Fundamentals of Software Testing” is the first module of the ISEB Software Testing Foundation course and examination syllabus. ISEB recommend that Software Testing Foundation students spend 20% of their study time on the Software Testing Fundamentals course section. “The Fundamentals of Software Testing” is also the title of the opening chapter in the official ISEB Software Testing manual.
Understanding the fundamentals of software testing is clearly crucial to achieving proficiency according to the ISEB software testing professional standards. But what, precisely, are these “fundamentals” of software testing, and what do you need to know in order to pass the ISEB Software Testing Foundation examination?
Why is testing necessary?
According to Peter Morgan (freelance testing practitioner and member of the ISEB Software Testing Accreditation and Examination panel), an unnecessarily high proportion of IT systems fail to fulfil expectations – or fail to work at all – because of insufficient software testing prior to release.
Software testing cannot guarantee against software problems or even failure, but it can minimise the risk of faults developing once the software is in use. In order to understand why software testing is necessary, it is important to consider the causes and impact of IT systems failure, and the crucial role that testing plays in Quality Assurance.
The ISEB Software Testing Foundation training-courses focus on five learning requirements:
  1. The potential impact of an IT systems failure;
  2. Causes/effects of software failure;
  3. Why testing is necessary;
  4. Testing versus Quality Assurance;
  5. Basic industry terminology.
What is testing?
Software Testing is a method of identifying faults in the product before it is released; this includes defects in the software code and its execution, as well as any potential gap between what the code is supposed to do and what it actually does.
The ISEB Software Testing Foundation exam requires students to:
  1. Know the basic objectives of testing;
  2. Understand how these testing objectives apply in the context of creating, using and supporting software (including the difference between testing and ‘debugging’, and the different uses of static testing and dynamic testing).
General testing principles
The ISEB Software Testing courses introduce students to 7 software testing principles:
  1. Testing can show that problems exist, but not that problems do not exist.
  2. Testing covers a limited range of sample situations, and is not comprehensive.
  3. The earlier a problem is found, the less it costs to fix.
  4. Defects will tend to cluster around specific areas (e.g. system complexity, or staff inexperience). These areas can be particularly targeted by testers.
  5. A set of tests, run repeatedly, will have diminishing effect.
  6. The type, design and focus of testing will vary according to the software tested.
  7. A test that does not reveal errors does not prove that the software is error-free.
Fundamental test process:
 
Software testing is not simply a case of reviewing documentation or running a software program to check for bugs. To ensure that the appropriate tests are operated effectively and return value on the invested resources, it is crucial that software testers carry out five basic activities, which the ISEB Software Testing guidance links to form a software testing process:
Test planning and control:
  1. Test planning defines what will be tested, how it will be tested, and who we will know when the testing is complete.
  2. Test control is an iterative activity that compares the progress against the plan, and adjusts the plan as required.
Test analysis and design:
  1. Test analysis considers the specific conditions to be tested, and how these test conditions are to be combined into test cases.
  2. Test design describes the expected outcome of the test, so that testers can easily recognise when a fault has occurred.
 
Test implementation and execution:
  1. Execution represents the most visible testing activity, and encompasses setting up the tests, generating test data, logging test activities and analysing the test results.

Author: Projectmanuk
Source:Link

Comments

Post a Comment

Popular posts from this blog

What is LCSAJ Testing?

Image
LCSAJ testing requires a model of the source code which identifies control flow jumps (where control flow does not pass to a sequential statement). An LCSAJ (Linear Code Sequence and Jump) is defined by a triple, conventionally identified by line numbers in a source code listing: the start of the linear code sequence, the end of the linear code sequence, and the target line to which control flow is transferred. Test cases shall be designed to exercise LCSAJs. For each test case, the following shall be specified: - the input(s) to the component; - identification of the LCSAJ(s) to be executed by the test case; - the expected outcome of the test case.
Read more

ISEB-ISTQB Sample Exam Paper 12

Image
1. Which of the following statements contains the correct use of the terminology? a) a fault by a person may introduce an error into the software that may cause a failure in operation b) a failure by a person may introduce a fault into the software that may cause an error in operation c) an error made by a person may introduce a fault into the software that may cause a failure in operation d) an error made by a person may introduce a failure into the software that may cause a fault in operation e) a failure by a person may cause an error in the software that may cause a fault in operation 2.   A reliable system will be one that: a) is unlikely to be completed on schedule b) is unlikely to cause a failure c) is likely to be fault-free d) is likely to be liked by the users e) includes a minimum number of components 3.   Which of the following statements about ‘Integration Testing in the Small’ is false? a) It can combine all the components ...
Read more

What is State Transition Testing?

Image
State transition testing uses a model of the states the component may occupy, the transitions between those states, the events which cause those transitions, and the actions which may result from those transitions. The model shall comprise states, transitions, events, actions and their relationships.   The states of the model shall be disjoint, identifiable and finite in number.   Events cause transitions between states, and transitions can return to the same state where they began.   Events will be caused by inputs to the component, and actions in the state transition model may cause outputs from the component. The model will typically be represented as a state transition diagram, state transition model, or a state table. Test cases shall be designed to exercise transitions between states.   A test case may exercise any number of transitions.   For each test case, the following shall be specified: -   the starting state of the component  ...
Read more