‘Test infrastructure as code’ should really be part of your Test Strategy or testing game plan for the lack of one.
From experience working with docker and kubernetes, the top benefits for have been:
– easily manage the setup of Ci jobs,
– changes can be tracked and become the single source of truth,
– easily deploy test automation tooling such as selenium and pact infrastructure,
– manage Cloud costs effectively,
– setup and tear down Jenkins nodes with ease,
– easily chain jobs and share volumes if needed,
– deploying across regions, teams and environments are a breeze,
– setting up end to end development and test tooling for manual testing becomes quicker.
#automation #cloud #testing #jenkins #aws #azure #cicd #kubernetes #docker
Having automated tests are great! … but not sharing the results or centralizing them is not so great. 😦
Your automated tests have undeniable business value, don’t be shy about it. Excellence does not happen overnight. So even if your tests are in early development, share the results with your team.
So what can you do?
- Setup a nightly run using some CI tool. I like Jenkins 😉
- Promote the results by using a dashboard, email or a tool like slack.
- Address failed tests daily. Fix them or add them to a backlog. Fix these soonest.
- Prep a backlog of test automation scenarios that the entire team supports and can contribute towards.
Visibility and Reliability are really important. This makes them trust worthy, needed… valuable.
Pursue it viciously. Take small incremental steps towards implementation.