UKStar 2018 – Our wrap-up

The Hiptest team is back from UKStar 2018 which took place in London. We were happy to meet you and to discuss about Behavior Driven Development, testing, automation and more. We attended to several very exciting conferences. Here is our recap.

Assurance, the evolution of test management? – Paul Gerrard

The most interesting statement in his presentation was the fact that DevOps is not an extension of Agile. It means a different culture and mindset. Governance for example, is trust based in Agile teams whereas it is Insight-Driven in DevOps. And this summarise quite well the Hiptest journey towards DevOps. “Show me the value and data” has become part of our culture. Measurement is another example of difference. Whereas Agile teams tend to avoid measurement (“no-estimation” movement…), DevOps teams are highly driven by analytics.
Here is the slide describing the comparison:
Agile vs DevOps teams
Paul Gerrard suggested a possible evolution for test management in DevOps context: ensuring successful software delivery by focusing on the flow of information and knowledge using all available analytics.

DevOps for the rest of us – Jitesh Gosai

Jitesh shared the brief history of DevOps including couple of interesting readings. The one that has inspired me the most in the past is “Lean Startup”. It is all about flow, feedback loop and continuous learning. Same goes for DevOps. Beyond the tools and automation there is the culture and mindset.
Analytics provide a great way to get feedback, learn about the product and inform future development. This was also mentioned in other presentations and I believe this is just the beginning.

Unity3D, a brief history of automation –Yan Drugalya

Adding automation to test an engine like Unity3D was a bit of a challenge for developers. To be able to easily execute tests on any development environment, they have implemented “Unified Test Runner” that allows to execute tests with very simple and easy to remember command lines.
They also used data analytics to speed-up test execution based on past execution results.

Testing though the log file – Johan Sandel

Log files can be a gold mine for anyone who knows how to handle them, and Johan is amongst them. He shared with us three ways to use the log file to increase product quality. The first one was the live notification of errors to the engineering team ensuring that everyone was aware of the problems that may happen to the users on the production site.
The second one was the use of the logs to enable the QA team finding patterns leading to errors and thus helping the development team fixing them. They also generated graphs from the logs to ensure a good coverage of the application’s testing.
Another use of the logs he proposed was to determine the users path on the application, which is generally not the one planned by the design and development team. Being able to understand the way people use an application can lead to an increase of the product’s user experience without the bias of selected users.

Shift left, shift right, the testing swing

Vincent and I had the opportunity to share our testing experience as part of a DevOps team. You can learn more about our own process in this post. We did a quick poll during the presentation about teams’ maturity. Interestingly about 25% of attendees deploy at least once a day in production and about 20% use analytics to inform future development. These ratio are much higher than last year and show an important increase in DevOps adoption.
We would like to thank you for attending our session and for all the great feedback you provided.
Laurent, Vincent and Aurélien.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s