Quality Assurance in REC Group

Quality assurance in REC Group

Contents

Projects

Competencies

Team profile

System integration tools

System verification toolsSystem verification tools

Management tools

2011-06-27© Research and Engineering Center www.rec-global.com1

Automotive

Cooperation with Continental AG

Responsibility for customizing products to customer specific requirements

Integration approach definition and execution

Test approach definition (test levels, acceptance/release criteria, test process definition), test plan preparation

Test specification preparation, tests execution:

Module tests

Integration tests

System tests

Test automation (mostly based on in-house solution ATE)

Python scripting

C++ (Test F-Block/ Test shadow)

© Research & Engineering Center, Wrocław, Poland2

Telecommunication

Cinterion Wireless Modules

Responsibility for:Protocol stack tests

AT commands functional testing

GPRS/EDGE/HSDPA/CSD functional testing

JVM, VME testing

Conformity tests (GCF)Conformance Testing for 2G/2.5G Technologies: GSM, GPRS,

EDGE, AMR (900/1800) EDGE, AMR (900/1800)

Conformance Testing for 3G Technologies: W-CDMA,

UMTS, HSDPA (FDD I)

SIM/USIM Testing

Radiated Spurious Emissions testing

Field Trials

GCF Qualified Networks

Skills:Mobile technologies: GSM/CSD/GPRS/EDGE/UMTS/HSDPA

Eclipse environment

CRTU protocol testing platform

Java,.C/C++

Test automation - Pegasus


Web applications

Cooperation with Polish Government, City of Wroclaw and PICZO.comResponsibility for:

Test concept preparationTest case implementation and execution

Analysis of customer requirements – iterative approach

Test automation


Test automation Aceptance tests with customer

Technology

JavaPerlMySQL

Test automation (mostly based on in-house solution ATE)

Python scriptingJUnitSelenium tool

Competencies


Competences

Verification• Planning of test approach,

test plan preparation

• Test execution on various levels:

Reviews

Module testing

Integration testing

System testing

• Integration

• Integration of SW modules, also coming from geographically distributed locations

• Gathering quality metrics with according to customer System testing

• Test techniques:

Specification based (functional and non-functional)

Structure based

Experience based

• Test strategy adjusted to

development model: V-model,

Agile, mixture...


with according to customer demands

• Resolution of conflicts in version control system

• Support for development in problem resolving

• Integration approach adaptation for customer needs

Verification levels

SystemRequirements

Acceptance tests

Customer Request

Product

Acceptance Testing

System Validation


SystemArchitecture

Technical Solution

Development & Testing

SystemIntegration

Module Testing(by developers)

Test Plan

System Verification

Quality first!

Acceptance criteria definition - exampleWeekly criteria

KPI’s – as defined by customer + REC internalTest report covering feature to be released given weekTest scope: at least 30% of system requirements covered by test cases, 100% of features to be released in given week

Major release criteriaSummary of KPI’s, performed on delivery + clear statement about KPI’s for major releaseTest coverage: 60% of system requirements covered by test cases, 100% of featuresReview of test report performed by CustomerAcceptance tests, performed on selected test cases – the scope must be defined before implementation starts, details to be confirmed at least 4 weeks before milestone. REC will provide compliance statement, considering available reources.

ExceptionsExceptionsIntroduced into release statementThe list of missing/not executed tests should be provided. For all the cases PL’s should be awared at least 4 weeks before milestone

Our team

• Test techniques based on

• ISEB foundation

• ISEB intermediate

• Experience in telecommunication

• GCF, protocol stack, but also Intelligent Network – performance verification

• Experience into embedded systems

• Wireless

•


• Automotive

• Experience in Web applications

• skills

• Perl

• Python

• C,C++

• Java

• Unix

• Oracle, MySQL

2011-06-27

# $Id: 541.py 726 2009-04-16 09:26:02Z wro00119 $

a = AcsPlugin()

a.logger.info('test case $Id: 541.py 726 2009-04-16 09:26:02Z wro00119 $ begin')

#enable notifications on VehicleFunctionsFB

EnableNotificationsOnFBlock(a, 0x005, 0x04)

#--------------------PRECONDITIONS-------------------------

a.logger.info('### preconditions begin')

statusFront.params = ['0', '55', '45', '55', '45', '83', '0x01', '0x02', '0']

a.putMessage(statusFront)

a.ignoreResults(10)

a.logger.info('### preconditions end')

#-------------------------STEPS----------------------------

# log begin of steps

a.logger.info('### step 1 begin')

# simulate rotary turn (on the user side) through TShadowACS:

turnRotary.params = ['3', '-1', '(1,1)']

a.putMessage(turnRotary)

#we’re waiting for result on the network side (we’re receiving request send to HVAC module

a.logger.info('### get result for step 1')

ret1 = a.waitFor(1.5, hvacTest)

ret2 = a.waitFor(1.5, hvacTest)

# condition for setting test result

if not(ret1 and ret2 and ret1.paramsi[2] == 1 and ret1.paramsi[4] == 11 and ret2.paramsi[4]

== 0):

raise TestStepFailed #step 1 failed

System integration – tools

support

Version control systems

Telelogic change (together with baselines concept)

SVN

Clear Case

Expertise:

- Installation

- Configuration

- Maintenance

- Support for geographically distributed development sites

- Support for development – conflict resolution, trainings


System verification – tools

support

•Very high flexibility – python plugins allow us

to adapt ATE to many different applications

and communication protocols.

•Detection of tool technical failures, i.e. bugs

ATE (automated test environment)


•Detection of tool technical failures, i.e. bugs

in test cases, bugs in plugins. If test case

fails, it throws specific exception –

„TestStepFailed”. Test case maturity levels.

•Automatically generated test reports,

coverage reports (like requirements

coverage)

•Support for various development models,

including agile approach.

•Automation: list of requirements, test cases

(description) and test case automation (code)

kept in one, consistent database.

2011-06-27

• Test runner

• Eclipse enviroment on RCP platform

•Test Cases written in Java

System verification – automation

tools

Pegasus SWT

•Test Cases written in Java

• Parallel tests execution

• Full event log file from executed test cases

• Communication with all HW interfaces (RS232, USB, I2C, SPI....)


System verification – automation

tools

Selenium - tool for automation Web testing

© Research and Engineering Center www.rec-global.com13

Selenium IDE tool JUnit test case

Automatic tests execution using Selenium server

System verification – incident

tracking tools

• project task tracking

• bug reporting

• bug tracking

• interface to version control

ClearQuest

© Research and Engineering Center www.rec-global.com14

• interface to version control

systems

• easy access to complete

incidents history

TRAC – project management and bug reporting tracker

• web-based tool

System verification – incident

tracking tools


• project task tracking

• bug reporting

• integrated Wiki

• interface to version

control systems

Methods for quality assurance

in the REC Group

For further information please contact:

Roman Sorokiewicz on [email protected] or

Tel: +48 (71) 711-8070; +48 660 430 104


Quality Assurance in REC Group

Technology

Transcript of Quality Assurance in REC Group