I’m always fascinated when I start to think about how large systems integrate with each other, how the pieces work (or don’t work) with each other, how a code change in one place could affect so much more. It’s like all of the small projects I have experience with amplified!
Michaelas podcast https://www.software-engineering-unlocked.com/
We’ll be adding all unanswered questions from the talk here so if we didn’t get to your question, don’t worry, we will find you an answer
If you’ve got a question you’d like to ask in advance, why not ask it now?
- shabbir: As now a days large scale systems are built incrementally and supported and operated with a lot of baked in tests – Do you think the hurdles of testing large scale system still exist?
- Elizabeth: Were there tests you decided to stop running while you were still compiling the data/asking questions, but before calculating the actual cost?
- Zivan Miljkov: What do you do with new test suits that are created during the analysis time?
- Madhuri: How often u go and check if tests are still relevant?
- Dennis dB: Who much did the investigation into costs cost?
- Paul Grossman the Dark Arts Wizard: Can you recommend best practices to manage source control merges with such a large team - I have nine team members practicing feature branch approach.
- Nathan Owen: Tying in to the talk about deleting tests earlier, did you find any tests where the cost of skipping a test never exceeded the cost of running it? Have you looked at applying this to identifying tests to delete altogether?
- Kishor Mohanty: That’s true that we can think about cost cutting, but what will happen to quality? How do we ensure that quality won’t impact while reducing/deleting some tests …