First, I think the current tutorial is beneficial enough to get anyone started with a decent understanding of RAML. That said, I am sure when the 1.0 spec is finalized, we’ll start to see a lot more documentation and tutorials around RAML, especially given the adoption of RAML.
There is a project in the Projects link to get you set up to use Sublime 3 with RAML syntax color highlighting, but unfortunately the only “ide” that offers some sort of code completion is the API Designer project. It’s not hard to set up if you follow that Github documentation, but it does limit you to using HTML 5 storage with no way to export the files short of copy/paste. It’s a shame they don’t add that feature to it. There is an alternative version of API Designer (forget the URL but it’s in a forum post somewhere around here) that a developer did to allow you to use Mongo DB and centralize the use of the API Designer project. I have that set up myself and it too leaves a lot to be desired, but does work by storing all the files in mongodb as well as provides info on how to set up a 2nd port to pull the files via GET calls to the urls. The primary issue with the API Designer is larger files cause it to get really sluggish, so if you can keep your RAML files small, you should be fine.
As for API test automation, yes it is definitely possible. The goal of RAML, in my opinion, besides making it easier to “sculpt” API endpoints and documentation, is to use it as a single source of truth document. If you look at the various projects here, you will find php, python, ruby, java, and more in terms of SDK and/or server side code generation. While most of them are not stable and have some issues, it’s possible to use RAML for all these purposes. There is the ABAO test project that will test your RAML doc against a deployed implementation of the API the RAML doc describes. If you couple that with the JAX-RS code generator, for example, you could generate stub server side code, WAR it up, deploy it and then run ABAO against that to test that your RAML doc is implemented correctly. You can also use the RAML to generate unit tests that you then run with each build iteration or any change commits to a RAML doc.
The bigger issue besides waiting on the 1.0 spec to be released (and then wait for all the projects to get updated to use the 1.0 spec) is that most of the projects seemed to have started but not had much work done lately… leaving us to wonder if they are dead projects or are they all just stalled waiting for the 1.0 spec to come out before they get completed.
Please jump in and help us make RAML that much better. Adding a language adapter to spit out junit automation tests would be a great addition that would benefit everyone in the community.