I personally don't like depending on services that lock me into their ecosystem and wouldn't want to impose that same type of lock-in onto other developers.
Do unto others, right?
TestFront's data structures are detailed but simple enough that it should be feasible to generate JavaScript code which could be read by other test runners - e.g., Cypress, Jest, Testing Library, Enzyme, etc.
The goal though is to make TestFront so good that people never feel the need to hit the eject button.
I personally don't like depending on services that lock me into their ecosystem and wouldn't want to impose that same type of lock-in onto other developers.
Do unto others, right?
TestFront's data structures are detailed but simple enough that it should be feasible to generate JavaScript code which could be read by other test runners - e.g., Cypress, Jest, Testing Library, Enzyme, etc.
The goal though is to make TestFront so good that people never feel the need to hit the eject button.