What role can a tester play in promoting good practices around continuous deployment and integration?
How do people deal with artefact promotion in multi-service environments?
Where do you believe good exploratory testing fits into CICD?
What type of tests should be part of a CI pipeline?
How can a team get to the point where they can safely do multiple deploys in a day?
How can a QA process be optimised for a CICD orientated approach in software engineering?
Why is automated performance testing often not added into CI?
Can one strategy for CI and CD work for many teams working across many different projects?
How can we better involve QA in the unit test case writing?
What tools or languages can you use to test the pipeline itself?
Do you have any tips on how to transition from a traditional waterfall release process into a CICD process?
How much do you believe practicing CICD successfully is founded on engineering culture compared to tooling and tech choices?
How can we make the most of branching and CI?
Do you recommend running a quick smoke test or full regression GUI automation suite during the pipeline?
Committing versus merging in CI?
In continuous deployment, how do you mitigate the risks of something being missed without final manual checks?
Do you have any suggestions for evaluating an existing pipeline and figuring out the best ways to adopt elements of CICD that may be lacking?
What are the important technical skillsets testers should have to work in a CICD environment?
What is the best way to incorporate and automatically test automated infrastructure changes?
How do you work with failing tests with issues outside of the teams control?
Have you had any kickbacks from a business about the number of changes/features being introduced in a CICD environment?
What metrics to measure success of a CICD initiative?
Do you recommend a different pipeline for emergency hot fixes?
When should we run automated API testing on a CI pipeline? tle
Description
Embark on a deep dive into the world of CI/CD and Delivery Pipelines with the phenomenal Abby Bangser. This Ask Me Anything recording sheds light on the intricacies of Continuous Integration and Continuous Deployment, drawing from Abby's vast knowledge and experience. Whether you're a novice trying to grasp the basics or a seasoned professional looking for advanced insights, this session is a treasure trove of information. Don't miss the chance to elevate your understanding of the agile software delivery process!
Get involved in the community discussion over at
The Club and find useful resources relating to this AMA there too!
Abby Bangser
Site Reliability Engineer (SRE)
Abby Bangser is a software tester with a keen interest in working on products where fellow engineers are the users. Abby brings the techniques of analysing and testing customer facing products to tools like delivery pipelines and logging so as to generate clearer feedback and greater value. Abby has a strong background in QA across software projects and platform engineering teams which she is now using in her new role as a Site Reliability Engineer (SRE).
Outside of work Abby is active in the community by co-leading Speak Easy which mentors new and diverse speakers, co-hosting the London free meetup Software Testing Clinic which brings together mentors and new joiners to the software testing industry, and hosting the London branch of #CoffeeOps meetup. You can get in touch easiest on Twitter at @a_bangser.
