@newromka@Debasisj@ptrthomas@SmartBear@cucumberbdd@specflow BDD is viewed as diff philosophy. It's about creating a clear tracking between reqs coverage and final tests. Like, here's the requirement, and here's the test that passed for it. Anything in between is the engineers' problem; the key is for the business to see clear traceability
Tricentis has abandoned SpecFlow but kept the trademark rights and tokens for new releases. The community has responded by creating a Reboot/alternative - Reqnroll: #OpenSourceCommunityhttps://reqnroll.net/news/2024/02/from-specflow-to-reqnroll-why-and-how/
after @SmartBear dropped support for @cucumberbdd and fired the last remaining developer, it looks like @specflow may go the same way with @Tricentis https://t.co/KSAv7T4loF
@Debasisj@ptrthomas@SmartBear@cucumberbdd@specflow Absolutely. In your case, the logical BDD layer just complicates life for test developers. However, BDD has its upsides - to me, it's a precursor to GenAI, which could easily take over the roles of BA/PO here. And, it might even eliminate the need to write tests as code later on
@DFischmeister@ptrthomas@cucumberbdd@SmartBear@specflow [2/2] 2023 hit IT hard, leading firms to drop non-profit ventures, even at the cost of their credibility. Big biz now ditches anything not directly making money, leaving behind abandoned FOOS projects but holding onto trademarks and release tokens. A classic: Dog in the manger
@DFischmeister@ptrthomas@cucumberbdd@SmartBear@specflow [1/2]Big players in the market, building platform solutions from a collection of open-source libraries, are buying up Trademarks and, consequently, the community (potential users). Either to just promote their solution to users or adapt the libraries to be part of their ecosystem