2

The short answer: you can't prevent regression in third party software. More detail: Third party software, as one of the comments mentioned, is outside your control. Since it's essential to your software, you have a few options in how you handle this. Regular smoke tests - Have a set of smoke tests that cover the essential functionality of the third party ...


1

Setting aside opinions people may have about SAFe and how Agile it really is, there is no conflict between SAFe as it is defined and TDD or BDD. In fact, the official safe write-up for teams suggests that software teams should be using those practices (https://www.scaledagileframework.com/agile-teams/). SAFe also still prescribes cross-functional dedicated ...


1

You can't really account for third party software being broken. It's outside of your control. But you should document it for several reasons: It might happen again and your documentation will give future developers/testers some insight. It justifies that the application is broken due to a third party integration. i.e.: it's not your fault. It creates a ...


Only top voted, non community-wiki answers of a minimum length are eligible