O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Gtd 2019 from zero to test! in 10 minutes. don't let your test infrastructure be your bottleneck - en - 1..0

51 visualizações

Publicada em

Maik Nogens at German Testing Day 2019

Publicada em: Software
  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

Gtd 2019 from zero to test! in 10 minutes. don't let your test infrastructure be your bottleneck - en - 1..0

  1. 1. From Zero to Test! in 10 minutes Dont let your test infrastructure be your bottleneck Maik Nogens
  2. 2. Maik Nogens Maik Nogens @MaikNog Quality Evangelist +49 151 544 22 475 maik.nogens@maibornwolff.de  Tester & Consultant  Designer of the Agile Unicorn  Community servant (QS-Barcamp, STUGHH, Meetup, ASQF, PotsLightning, GATE, …)  Inventor of the original STWC (Software Testing World Cup)
  3. 3. Data and facts of MaibornWolff SBB CFS FFS 30 Mio. sales * 450+ employees 8 years in a row 1 week R&D per year Berlin Frank- furt München Augsburg 20 nationalities Estimated for 2017 Hamburg
  4. 4. Shape IT for the people you work with DevOps Early phasesIT strategy Web engineering Internet of Things Mobile Engineering Test automation Test management Test consulting Enterprise ApplicationsSalesforce Digital trans-formation IT-Consulting Software development Testing Blockchain Software audits and reorganisation
  5. 5. Services Test Environments Tools Test Data Connected systems Hardware What is Testinfrastructure?
  6. 6. • Test data are a part of test infrastructure •„Valuable“ Test data is: •... well maintained, e.g. they are as current as needed. •... embedded in a change process, which on the one hand offers control over the data pool and on the other hand offers the flexibility for a lean and fast change process. •... structured and available in different shapes. Test data – metalevel, what why how so? With these preconditions test data are part of the test infrastructure and can be deployed as fast and efficient as code, configurations and hardware.
  7. 7. Marketing •Different sets for different focus: •Standard •Most important data combinations for most important business flows •Regression •More combinations of business process •Load •Synthetic amount; detailed combinations are not important •Marketing •Handmade data pool •For advertisement and marketing Test data – case study Load Regression Standard
  8. 8. •To change test data in your own control offers flexibility. •With more folks involved and more test data the overview gets more complex. •Which impact has a change of test data onto others, who also uses this test data? •A central, but flexible change process helps Test data – change process - metalevel, what why how so? ?
  9. 9. Test data – change process – case study New
  10. 10. •Largely separate from the production environment, so that the test objects do not cause any damage to the productive operation. •As closely as possible to the actual production environment. Wikipedia (DE and EN analogous) Test environment – metalevel, what why how so? • It is practical to have different setups of test environments, which gives balance between fast availability and closeness to production setup. • A common scale is … • DEV – close to development with an atomic / single focus • Integration – integrative focus of components / modules • Pre-Production – Focus on business processes; systems and components are real
  11. 11. Test environment – case study Max. 3 test environments M D M D F S S X X CPU: 2 RAM: 4 GB DB, HDD, …. CPU: 8 RAM: 16 GB DB, HDD, …. Marketing, Training, Design Dev, Test, PO Tester Profile < 10 minutes Service Config A Service Config B
  12. 12. •A sequential change process for test data has waiting times. •When needed folks are not available or tickets won’t be worked on in a timely manner, the whole chain is blocked.  Open point; still in process to be solved. •Hardware does not scale with demand. •300+ users are regularly using multiple test environments.  Limit it to 3 per user and shut them all down on Friday evening. •Account for special cases. •Long running tests should not be turned off.  Put them on a “Exception list” Which challenges did we have to solve and what did we learned from it?
  13. 13. When infrastructure is easy to use, everyone wants and will use it. The practical impact is huge, when everyone can create test infrastructure on demand. It becomes routine and daily practise.  10 minutes from “Zero to Test!” is reality. Conclusion YMMV
  14. 14. Questions? Question! • How do you structure / administrate your test data? • How do you handle test data requirements from your teams / organisation? • Which test environment ist your common one ; which are you using the most?