Yes, the decision to end the Script Developer was a hard one but we have tried to find and develop a compatible solution. While we have had that new project underway, we found out that it is not economical viable to finish the project. Basically what we invested in test automation and Script Developer over the course of the last 10 years, would had to be spend right away for the rewrite.
Additionally some of our existing Script Developer users already went straight Java and just exported test cases or even worse, abandoned the approach because they needed something with higher power aka a programming language. Also BDD (such as Cucumber) has gained a lot of popularity and especially with customers that don't have large development crews, BDD just works better and also documents things nicely.
Also in project pitches, Script Developer was sometimes rejected because it was and is proprietary.
That being said, we have basically these things to offer:
- XLT 4.10 will deliver a changed export to Java that makes maintaining the test cases in code easier and the API nicer. This helps you to continue with all your test cases and the set up tool chain, except that you have to go code to update CSS selectors and such things.
- Your existing test cases won't break, you just cannot use the UI to maintain them anymore. You have to execute them using WebDriver - what you probably already did - and basically edit the files (XML, properties) instead.
- We are working on a test framework template that utilizes all well-known Open Source components such as Selenide, WebDriver, Maven, Cucumber and enriches these with data support, page concept, multi-browser, and visual verification as well as a first template to start from. In later versions, we will also bump up the reporting capabilities because that it an often asked topic. This new project will be 100% Open Source and independent from XLT. It will give you a solid foundation to build your automation on it as well as due to full code access, you can extend and fix things easier yourself and last but not least, you can google for a lot of solutions to your daily problems.
- When your IT permits, stay on Firefox ESR for test automation and you will be able to continue to use Script Developer as long as the operating system supports this Firefox version and your application works with this older FF. We are willing to support this as part of a support contract and deliver fixes when needed.
We plan to introduce the new project (code name Neodymium for now) in December and for all the users around our headquarters in Jena, Germany, we will have a get-together to show and discuss it.
Hope that helps and feel free to ask any question any time. We once again apologize for the inconvenience this causes but at the end, Mozilla trashed our 10 year investment in their API by abandoning it. We basically face the problem you face, everything done so far, all the money spent... wasted and there is no real migration path available either. One of the reason why Firebug died as well.