Neste: How to Build Business Case, Ramp-up and Run SAP Test Automation Factory by Wout Boer (Neste) & Rohit Chandra (Sogeti).

1. 1

2. [NOTE: 2018 figures.]
• People: We are 5,468 dedicated professionals – Exceptionally clear
understanding of vision and strategy among personnel
• Impact: In 2018 our products helped reduce greenhouse gas emissions by 7.9
million tons. Neste placed 3rd on the Global 100 list of the world's most
sustainable companies. This is the 13th time that Neste is included on the list.
The company has been included on the list for longer continuously than any
other energy company in the world.
• Innovation / R&D: We explore how to make even higher quality products from
even lower quality raw materials – almost 80% of our renewable fuels are
produced from wastes and residues
• Business: In 2018 the comparable operating profit of Neste was 1,422 MEUR –
our forward way of working ensures constant development of efficiency and
operational excellence.
2

3. Building Test Automation is like building a car.
This VW has a solid platform that is also used for this luxurious Bently.
You can build something small and fast like a kart which serves only one purpose
or you can build a platform that can be re-used as a solid base for other cars.
With this I am not saying that we want to build a bently but as this example shows
having a solid base allows you to build anything between reliable but functional
and the best there is. The initial progress will be slower of course because of the
build of the platform however this will be a solid base for years to come.
Platform info incase of questions:
Volkswagen D1 platform
Continental Flying Spur
Volkswagen Phaeton
3

4. This has been and still is a journey where we knew a direction but as questions rose
we were able to answer them. Just to clarify this is still all very early phase and we
are still learning and adapting.
As the project progressed the need for test automation became clearer and clearer
as challenges rose.
A common problem nowadays is the resource availability this also was the case for
Neste with all the projects going on simultaneously. As the project went through it’s
delivery phases the amount of work in testing grew as did the needed regression
testwork.
Until then there was no test automation service available at Neste. Long time ago ,
way before my time, only some experiments had been done with test automation.
At start no data was available to build a business case on. By using the information
available in the test tools used (HP/ Micro focus toolset) we have been able to build a
business case for test automation.
4

5. Using HP ALM businessviews to combine test execution data (run steps, runs, test,
test set etc.) averages could be found allowing to calculate the cost of one
execution that could then be extrapolated to several executions.
Go over the calculations left and right.
In addition to this data, data from e.g. service now can be used to get defect
frequency and average outtage time. This multiplied by the cost of an outtage can
also be taken into account.
5

6. 6

7. In the current slide, we will be talking about the Automation approach which
we have taken at Neste.
We have our automation service at Neste which caters TWO very important
aspects of any Automation project.
1st: Development:
Constant Development of automation script for the existing SAP processes in
the form of content Sprint. We analyse the content from previous testing
phases for e.g Beagle OP2 and Beagle OP3 and we take those items in the list
of backlog items for automation. After that we do reusability check of those
content which I will be talking about in next slides.
2nd: Maintenance:
Maintenance of already created script in Sprints by our Run & Maintenance
services
7

8. Confirmed business processes automated and runnable nightly within regression test suite.
By having Sprint 0, we made sure that we have a solid platform on which we can build our
service which is maintainable and expandable.
8

9. * Reusability of already existing processes
* Impact analysis if any process is being changed
9

10. We work as a one team to make this happen.

11. 11

12. In the Business case it was calculated that there are approx 6 test steps and in our
actual Sprint 1 we have found that there are approx 6.8 screens per script.
So we are going to get the payback from this automation service in less than a
year which was projected in the Business case.
12

13. Automation and manual per unit price

14. 14

15. This slideshow the various options for execution of E2E test scenarios.
The variation is in the execution responsibilities as well as in the level of automation.
It is obvious that fully automated scenario execution is the most economic choice.
The execution is part of a service that already is up and running, because of this there
is no additional cost, this is regardless the number of times the scripts are executed.
For the other options the cost is per execution of the scenario.
If you look at the difference between the Manual execution options the Test Partner
execution might seem more expensive. However when you consider the Neste
Business resources being free to do other work when the Test Partner executes the
tests this turns out to be the more economic choice. (xxx-xxx=xxx euro extra cost as
compared to Neste Business execution and this would free up the Neste resource for
x.xx hours. Which would be an experienced business resource available to us for an
hour rate of xxx/x.xx=xx.x euro per hour)
To take the burden of execution from Neste business people, we have defined 3
managed test execution mechanism by which we will support the Neste people.
15

16. Landed resource is key in bridging between Automation Team and Solution
managers. We would have had even more benefit if the whole automation
team would have been on site for the first period.
Keep ALM up to date and include the test data into the scripts (dynamically).
We could have made better use of the scripts already available in ALM if we
would have kept them in a better shape.
Recording of script execution saves time for business. When recording the KX
sessions with business the recording helps when the automation team has
questions about the process in the majority of cases just looking at the video
answers the question.
Approach chosen: structured but flexible helped in optimal use of limited
resources
16