Continental Test Lab: August 2014

Continental Test Lab
August 2014
Interior Infotaiment and Connectivity R&D Romania

Agenda
1Day 1 - The need of testing, Principles of testing, SDLC

2Day 2 - Test Levels and Functional Testing
3Day 3 - Non-functional testing and Defect LifeCycle
4Day 4 - Test Types

5Day 5 - Test techniques
6Day 6 - Discussion over homeworks

2 11-03-26 Autor, © Continental Automotive Romania SRL
Table of contents
1Test Levels
2Functional testing

3 11-03-26 Autor, © Continental Automotive Romania SRL
Test Levels
Test Levels
Testing is performed at different levels involving the complete system or parts of
it throughout the life cycle of a software product
A software system goes through four stages of testing before it is actually

deployed:
Unit/Component
Integration
System
Acceptance
The first three levels of testing are performed by a number of different

stakeholders in the development organization, where as acceptance testing is
performed by the customers
18 August 2014 , © Continental Automotive Romania SRL

Test Levels – Component testing
Component testing
Component testing (also known as unit, module or program testing) searches
for defects in and verifies the functioning of software modules, programs,
objects, classes.
Component testing occurs with access to the code being tested and with the
support of a development environment such as a unit test framework or
debugging tool.
One approach to component testing is to prepare and automate test cases

before coding (this is called a test-first approach or test-driven development)

Component testing
Button from an Xbox Controller
We can test the 4 directions
We can test that on press it triggers an event
We can test that on continuous press it triggers multiple events
We can test 2 directions at once

Component testing
Microsoft Paint – Color tab
Select the red color
Enter in the edit colors menu and select magenta
Select the second Color tab

Component testing
Printer – Ink Cartridge Slot Component
Insert the Colored Cartridge into the slot
Insert an empty Colored Cartridge into the slot
Insert a B&W Cartridge into the Colored Cartridge slot
Check if the contacts of the Slot are in the proper order

Test Levels – Integration testing
Integration testing
Integration testing tests interfaces between components, interactions with
different parts of a system, such as the operation system, file system and
hardware, and interfaces between systems.
There may be more than one level of integration testing:
Component integration testing tests the interactions between software

components and is done after component testing
System integration testing tests the interactions between different systems or

between hardware and software and may be done after system testing
The greater the scope of integration, the more difficult it becomes to isolate
defects to a specific component or system, which may lead to increased risk
and additional time for troubleshooting

Integration testing
Xbox Controller connected to a console
Check the data flow from pressing a button
to the controller CPU and transmission chip
Verify the wireless reconnection of the controller to
the console on start
Check the data flow between controller and
console on multiple button presses
Press the menu button, the event is sent to the
console and the menu is visible on the screen

Integration testing
Microsoft Paint
Check that when selecting a new brush,
the event is sent to the OS and the mouse
icon is switch to the new brush
Copy a image to the clipboard and try to paste it into Paint
Save the new picture to the E drive and check if the file is saved to the file system
Open a bitmap file from D drive

Integration testing
Printer
Remove the paper from the tray slot and print
(The detection module for the paper will need to inform the main module that there is no
prepare, so the printing is cancelled)
Install the printer on windows XP, open document X in MS Word and print
Open the printer without a Cartridge inserted
(the system will detect the missing cartridge and inform on power on event)

Test Levels – System testing
System testing
System testing is concerned with the behavior of a whole system/product.
The testing scope shall be clearly addressed in the Master and/or Level Test
Plan for that test level.
In system testing the test environment should correspond to the final target or
production environment.
System testing may include tests based on risks and/or on requirements

specifications, business processes, use cases or other high level text
description or models of system behavior.

System testing
Move the right joystick up
Press the Y button and then the A button
While in Menu press the Back button
Move the left joystick in all directions
Remove the batteries from the controller

System testing
Draw a red line with brush 1 and size 2
Select the shape Circle
Change the color to Green
Draw a Circle
Access the Edit Colors menu
Select from tools the bucket
Change the color to green
Use the bucket to change background in green

System testing
Power on the printer and print in color document X
Print in black and white on two sides the document Y
Print a document Z with high quality preset
Leave the printer powered on for one week
Print document R at high speed with low quality preset
Check the alignment in page

Test Levels – Acceptance Testing
Acceptance testing
Acceptance testing is a test conducted to determine if the requirements of a
specification or contract are met.
The goal is to establish confidence in the system, parts of the system or

specific non-functional characteristics of the system.
Finding defects is not the main focus in acceptance testing.
Typical forms of acceptance testing include the following:

User acceptance testing – verifies the fitness for use of the system by business users.
Operational testing – the acceptance of the system by system administrators (testing of

backup,disaster recovery, user management, data load and migration tasks)
Contract and regulation acceptance testing – is performed against a contract`s acceptance

criteria for production custom-developed software
Alpha and beta (or field) testing – software often want to get feedback from potential or
existing customers in their market before the software product is put up for sale

Acceptance testing
The product can be launched for a Alfa or Beta testing
The functions from the controller are respecting
the contract
The buttons alignment are right
The grip is as requested

Acceptance testing
Is it compatible with Windows 7 and 8 as in contract?
The setup works as expected
The GUI layout respects the specifications

Acceptance testing
Behavior at increasing speed
Density printing profile is respected
Color density fluctuations
Alignment check

Test Levels – Verification and Validation
The four stages of testing have been illustrated in the form of what is called the
classical V

Verification
"The process of evaluating a system or component to determine whether the products of a

given development phase satisfy the conditions imposed at the start of that phase.“
Verification simply demonstrates whether the output of a phase conforms to the input of a
phase as opposed to showing that the output is actually correct.
Verification will not detect errors resulting from incorrect input specification and these
errors may propagate without detection through later stages in the development cycle.
According to IEEE Std 1012-1998/2004

Validation
"The process of evaluating a system or component during or at the end of the

development process to determine whether it satisfies specified requirements.“
It is not enough to only depend on verification, so validation is necessary to check for

problems with the specification and to demonstrate that the system is operational
“A written guarantee that a system or component complies with its specified requirements
and is acceptable for operational use."
According to IEEE Std 1012-1998/2004

Continental Test Lab: August 2014

Uploaded by

Copyright:

Available Formats

Continental Test Lab: August 2014

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Continental Test Lab: August 2014

Uploaded by

Copyright:

Available Formats

Continental Test Lab

Interior Infotaiment and Connectivity R&D Romania

1Day 1 - The need of testing, Principles of testing, SDLC

4Day 4 - Test Types

Interior Infotaiment and Connectivity R&D Romania

Interior Infotaiment and Connectivity R&D Romania

A software system goes through four stages of testing before it is actually

The first three levels of testing are performed by a number of different

Interior Infotaiment and Connectivity R&D Romania

18 August 2014 , © Continental Automotive Romania SRL

One approach to component testing is to prepare and automate test cases

Interior Infotaiment and Connectivity R&D Romania

18 August 2014 , © Continental Automotive Romania SRL

Button from an Xbox Controller

We can test the 4 directions

We can test that on press it triggers an event

We can test that on continuous press it triggers multiple events

We can test 2 directions at once

Interior Infotaiment and Connectivity R&D Romania

18 August 2014 , © Continental Automotive Romania SRL

Select the red color

Enter in the edit colors menu and select magenta

Select the second Color tab

Interior Infotaiment and Connectivity R&D Romania

18 August 2014 , © Continental Automotive Romania SRL

Insert the Colored Cartridge into the slot

Insert an empty Colored Cartridge into the slot

Insert a B&W Cartridge into the Colored Cartridge slot

Check if the contacts of the Slot are in the proper order

Interior Infotaiment and Connectivity R&D Romania

18 August 2014 , © Continental Automotive Romania SRL

There may be more than one level of integration testing:

Component integration testing tests the interactions between software

System integration testing tests the interactions between different systems or

Interior Infotaiment and Connectivity R&D Romania

18 August 2014 , © Continental Automotive Romania SRL

Check the data flow from pressing a button

to the controller CPU and transmission chip

Verify the wireless reconnection of the controller to

the console on start

Check the data flow between controller and

console on multiple button presses

Press the menu button, the event is sent to the

console and the menu is visible on the screen

Interior Infotaiment and Connectivity R&D Romania

18 August 2014 , © Continental Automotive Romania SRL

Check that when selecting a new brush,

the event is sent to the OS and the mouse

icon is switch to the new brush

Copy a image to the clipboard and try to paste it into Paint

Open a bitmap file from D drive

Interior Infotaiment and Connectivity R&D Romania

18 August 2014 , © Continental Automotive Romania SRL

Remove the paper from the tray slot and print

Open the printer without a Cartridge inserted

Interior Infotaiment and Connectivity R&D Romania

18 August 2014 , © Continental Automotive Romania SRL

System testing may include tests based on risks and/or on requirements