Case Coriant Tellabs - Agile Testing Implementation 22.5.2014
1. Hannu Tuomisto, Sr Mgr Engineering
Case Coriant (ennen Tellabs) -
Ketterän testauksen käyttöönotto
22.05.2014
2. Scrum model at Tellabs Finland
• Moved from waterfall model to scrum model in
software development 2 years ago
• New feature test engineers were assigned to scrum
teams together with software developers
• 20 parallel scrum teams, team size 10+
• Single code base called MCL (master code line)
where all the functionality is developed
• Continuous integration with smoke testing in use
• Regression testing is outside from the scrum process
• System testing is outside from the scrum process,
even though they have voluntarily started to use
scrum in their own team as a daily tool
TELLABS CONFIDENTIAL PROPRIETARY 2
3. Goals for the scrum development
• Faster development
• Better collaboration
• Simultaneous test development in parallel with
the SW implementation
• Improved quality
• Get rid of separate testing phase in the end of the
project
• Faster testing = short feedback loop
• Faster test automation
May 27, 2014 3
4. Challenges
• Our fear was not that test engineers would loose
jobs because programmers would write all the
tests - quite the contrary, we were afrait that the
testers would end up doing low level module
testing for programmers
• Adjusting to corporate waterfall process and
quality structure
• Keeping MCL quality at good level all the time
(pass rate up, reported bugs fixed fast)
TELLABS CONFIDENTIAL PROPRIETARY 4
5. Other changes in testing
in addition to scrum model
• Enhanced test development guidelines
» Test spec templates to help develop full coverage tests
» Requirement mapping
• Extended Scripting rules for test automation
» Helping reusability
• Peer reviews
• Dynamic test environment model taken into use
• Extensive automated test reports created to
support business and project management
• Clear criteria for feature ready and regression
transfer
TELLABS CONFIDENTIAL 5
Mitigating the risk that scrum teams would work in silos
6. Automation
• Test automation is a must, continuous retesting
needed in regression testing and in new feature
testing
• Automation done with TCL scripts
• Tests automated in NF testing in scrum teams and
selected tests transferred to Regression testing as
soon as they are ready and tests are passing
• Regression testing almost completely automated
» Not only test cases, but also test execution
• Regression testing running 24*7
• Regression failure: Automated Iterative ”KRH”
method systematically launched to locate failing sw
label
» Significantly shortening the fixing time
TELLABS CONFIDENTIAL 6
8. Application testing
• Large configurations used in testing
• Concentrating on scalability, performance, load,
stress, robustness and stability testing of the
release
• Specified profiles in use, mimicing customer
networks
» Specified test environments
» Specified configurations
• Challenge: Finding quite difficult bugs and late in
the project
• Need to start as early as possible
TELLABS CONFIDENTIAL 8
9. Going forward...
• Define test architecture for test development
» Faster test case development
» Straightforward test case building blocks
• New layer between smoke testing and weekly
regression testing: Daily regression
• Take new sw simulator into use in test development
and in test execution to enable earlier start in testing
as well as helping to keep the budget
• Engage scrum teams with system testing to make
sure that challanging large configurations are tested
early
• Tester tasks vs. Programmer tasks
» reach genuine Whole-team approach attitude
TELLABS CONFIDENTIAL 9