We have an Angular app w/ OAuth flows and connections to outside apps. We started with Protractor running locally and on SauceLabs, but it hasn't seen much love because adding new tests takes time, especially for complicated stuff like oauth flows.
Your product should allow our "Product guys" and QA guy write the smoke tests in much less time and maintain them without having to write code or take up developer time, which is huge in a team of 2 guys who write front-end code and would be maintaining the tests.
The only real issues I have right now are 1. Errors can be hard to track down since there isn't any console output. That's something I miss from SauceLabs which was a huge help. 2. Smaller, but annoying, pasting isn't allowed when creating a test. This is painful for username/password entry. It would also be nice to use some kind of variable to ease this. 3. I'm unsure of pricing. When I'm logged in, I see that I have the free plan, but I see no limits or details about the plan.
Other than that, it was a great feeling to get a basic smoke test, plus jenkins integration, plus flowdock integration within an hour of discovering the app. Again, great job!
About pricing, you can test all features for free. If you like it and continue to use it, you can subscribe to one of our plans.
Copy pasting is a feature which we haven't solved yet. It would definitely be a huge productivity boost when making traces.
Console output is in our backlog but currently we focus on more important issues.
Questions:
1. When creating a trace, how do you specify when you're finished?
2. Is there a way to set a single trace to run on all browsers?
3. How do you specify what constitutes a "success" vs. a "fail" for any given trace?
2. Yes, from Dashboard it's currently FF&Chrome only, but via API you can include IEs. I can help you to get started (mailto arto@usetrace.com)
3. If a Trace can be walked through it passes. A Trace includes steps like clicks on buttons and checks (explicit things that must be visible on the page, e.g. text or other elements).
I haven't used either extensively, but they look similar in a few ways, yet different. I am curious if anyone with knowledge of the two could elaborate on the differences.
In Rainforest you define tests by writing instructions for human testers. Reports only tell you if a test was successful or which steps succeeded / failed. It takes close to half an hour for one two step test to complete in five browsers.
Cheers, Eero CEO of Usetrace http://twitter.com/EeroHeroHeino
One customer, that didn't have any automated testing, was able to create 40 cross-browser traces and integrate runs with Jenkins in two days. The average running time for their whole set is about 3 minutes.
When you register account, you can test for free. CI and reporting are under settings.
Personally after doing programmed Selenium tests for 9 years, I have learned that when releasing software daily, scripted tests lag all the time behind development. Providing a simplified testing tool that allows easy trace creation and maintenance without programming is needed.
However traditional record & playback tools are not working for agile teams due to maintenance burden. Usetrace brings concepts from the scripted testing available to non-programmers.
I can go through a sign up flow and then grab the last user with Ruby and do actual checks on it's methods and members, and then go back to browser navigation. This seems like a less free way to do fewer checks with a prettier interface.