Embed Size (px)
Citation preview
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 1 © Nokia 2014
Automated software testing tools and big data
testing Presentation for TTY course TIE-21204 Ohjelmistojen testaus
Tuomas Lunti
NAdC / Leena Rasinaho
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 2 © Nokia 2014
Nokia Networks business in Finland
NAdC / Leena Rasinaho
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 3 © Nokia 2014
Networks business in Finland
• Head office in Espoo; other offices in
Oulu and in Tampere
• One of the main R&D locations for
Networks
• Full range of operations including
manufacturing of base station
products in Oulu
• Key customers: Nationwide
operators Elisa and TeliaSonera;
Finnish Railway Administration
(GSM-R)
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 4 © Nokia 2014
Employees
• 6000 employees
•Over 10% of total Nokia employees
• 3700 R&D employees
• Approximately 400 manufacturing
employees
• Employees by location:
•Espoo 3 000
•Oulu 2 300
•Tampere 700
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 5 © Nokia 2014
Locations
Espoo •Head office functions
•End-to-end Mobile Solution Center
Oulu • Radio Research & Design Center
•Base Station manufacturing
Tampere •End-to-end Network Operability Center
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 6 © Nokia 2014
Ecosystem • Local universities providing access to latest technologies which
utilized via coop projects and thesis workers for our R&D projects
• Lots of user experience and process automation expertise
in local companies. Coop projects with TUT, UTA, TAKK and TAMK
• Close, regular and trustful relationship with Tampere City officials and
mayor to discuss the future plans mutually. Visible e.g. via Tampere
spirit Training where public funding available
Highlights
• End to end Operability, User Experience and Process Automation
• Operations Support Systems
• GSM Base Station Controller and WCDMA Radio Network Controller
• SW maintenance services
• Real-time data processing for CEM via Traffica
• Shared Reference Network lab and Global OSS Lab
Technology Expertise
• System integration competences for OSS and end-to-end operability
• Customer experience management, Traffica, Service assurance
• GSM / WCDMA Controller Specification, SW and I&V
• System Modules, System on Chip development
Tampere – SoC Development, Operations Support Systems and Customer Experience Center
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 7 © Nokia 2014
Automated software testing tools and big data
testing
NAdC / Leena Rasinaho
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 8 © Nokia 2014
NetAct NetAct
(regional)
General Architecture in NetAct
3RD party tool
Other
vendors
NEs
Alarms
Configurations
Measurements
GSM
WCDMA
LTE
MVI
CORE
Global products (e.g. Advanced Configurator,
iSON Manager)
3RD party tool
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 9 © Nokia 2014
Continuous integration (CI) is a
practise where all developers
merge their working branches to
main branch at the end of the day.
This ensures integration problems
are found faster and no large
integration problems can arise.
Continuous integration
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 10 © Nokia 2014
Code creation and testing before commit
Create/refactor
code
Create unit
testing
Review code
with team
member
Development team +
architect(s)
iterative
process Test code by
locally building or
debugging in IDE
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 11 © Nokia 2014
Build server
Unit testing – Junits – first level of regression testing
Building the software
Running static analysis tools to check code quality.
Review code in review tools.
Free build server tools
Build server: https://jenkins-ci.org/
Static analysis tool: http://www.sonarqube.org/
Build server – after commit
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 12 © Nokia 2014
Unit testing
Unit tests are most important test cases
Unit tests gives fast feedback to developers normally in seconds
Unit tests can be executed already in local environment
Unit tests are stable if done in correct way
Unit tests should test unit ie classes.
Static analysis
Keeps the code in good shape
Sometimes finds potential problems like null pointer issues
About unit testing and static analysis
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 13 © Nokia 2014
Integration testing pipe is constructed on many blocks to help locating
problems easier and faster.
Examples of test automation frameworks:
https://cucumber.io/
http://robotframework.org/
Automated Integration testing
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 14 © Nokia 2014
Big data testing
NAdC / Leena Rasinaho
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 15 © Nokia 2014
Big data testing - problem
The problem: about 300k BTS deployed to customers and most of them have
different configuration. How to test all the configurations?
Large number of different configurations create two problems:
1. Creating a lot of test cases
2. Time needed for executing the test cases
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 16 © Nokia 2014
e2e Test environment
Creating the testcases:
Too much automated test cases are hard to maintain and require lot of work to create.
Good way is to separate test automation logic and test data. For each configuration there can be
only a test data and the logic is common.
Create automated way to create the test data for each BTS configuration.
Time:
Optimize the test case to work as fast as possible. This normally means optimize the code what is
under testing. Customers will also like when their applications work faster.
Paraller execution when running the test cases. This requires hardware but not much if the code is
done properly and does not use a lot of resources (cpu/ram).
Automated testing is easy for good software and often test automation problems are more
software problems than test automation problems.
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 17 © Nokia 2014
New software build
Test execution machine
Run test cases and collect logs
from workers. Constructs one
single report.
Worker2
Deploy Software and run tests in
paraller.
Paraller Test environment
Worker1
WorkerX
Worker3
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 18 © Nokia 2014
Summary and Q&A
Summary and Q&A
To change the document information in the footer, press [Alt + F8] and use the “FORM“
R 18
G 65
B 145
R 0
G 201
B 255
R 104
G 113
B 122
R 216
G 217
B 218
R 168
G 187
B 192
Core and background colors:
12/10/2015 19 © Nokia 2014
