Comments by "" (@d3stinYwOw) on "5 Reasons Your Automated Tests Fail" video.

Really great video! I have some points though: 1. For environment to fail sometimes you don't need to break configuration. It can just happen to have issue with HW debugger <-> DUT data exchange. What to do in that case? 2. About Versioning - what about more 'isolated' test systems, where people who write test don't see the code, and work using black/greybox techniques? 3. System behaviour - it can be the case for DUT to stop behaving fully deterministic due to infancy of the libraries from vendors, like Hardware Abstraction Layer, or not-widely used part of used RTOS ;) I know, that I write from more embedded space of testing work, where you have dedicated HiL instances for various tasks, like data injection or non performant HiLs, but those are also valid things to consider when trying to deal with test intermittency :)
7
@ContinuousDelivery It depends on whole organization of a project, or even a company - not everywhere system qualification/integration testing is tightly connected with purely software integration/qualification testing. Even them can be disconnected from tests written by developers themselves :)
2
@ContinuousDelivery For point 1 tho, HW does not need to break to have this kind of issue. It might be the case that SW which we don't control does not behave like we expect it to do, and to replicate this, you need really specific setup. For point 3, it's doable only when SW devs write this HAL. Sometimes you can get this only as library + headers to link against during linking stage when building SW.
2
About Tesla - yes, they did that rewiring and it's great, but still didn't fixed NFC security flaw and Pin security based authentication flaw as well, which both of them are really easy to exploit. Additionally, their pipelines don't help so much to push FSD forward to stop being glorified cruise control
1