I think we underestimate the pervasive use of Excel in Fortune enterprise environment. I've seen people use Excel for the most ridiculous things. Excel is religion for some people.
This would be fantastic for automatic canned-testing that is run on regular basis, akin to quick diagnostic.
> I think we underestimate the pervasive use of Excel in Fortune enterprise environment.
I'll vouch for that. However, I really wonder whether automated testing is something that needs to be in the hands of people who are more comfortable with Excel and less comfortable with, say, YAML?
Also, I'm not sure if it's the responsiveness of the website being tested that makes this so slow, but it takes a very long time for the tests to complete. Line up a couple hundred tests and you're looking at very long run times. That's going to inhibit adoption for anyone who knows how quickly headless browsers can complete integration tests.
Great feedback. Supporting YAML syntax makes sense, and will put that on the roadmap. Regarding slow times, the automated tests have sleep commands for 4 seconds (intentional for now, but not required) between test scripts, this can be re-fined and improved quite a bit.
Thank you for the feedback.
The admiration for Excel is sometimes mind-blowing, but it is true. Excel was selected primarily for its mass adoption rate, and the likelihood that testers already use Excel for reporting purposes. Regardless of the test automation solution, it seems reporting naturally finds it way back to Excel.
We are currently using and enhancing testx. This does use the advantage of Excel and protractor. It's open source and available on github : https://github.com/greyarch/testx
A library for executing MS Excel based, keyword driven tests with Protractor.
6 comments
[ 3.2 ms ] story [ 22.3 ms ] threadThis would be fantastic for automatic canned-testing that is run on regular basis, akin to quick diagnostic.
I'll vouch for that. However, I really wonder whether automated testing is something that needs to be in the hands of people who are more comfortable with Excel and less comfortable with, say, YAML?
Also, I'm not sure if it's the responsiveness of the website being tested that makes this so slow, but it takes a very long time for the tests to complete. Line up a couple hundred tests and you're looking at very long run times. That's going to inhibit adoption for anyone who knows how quickly headless browsers can complete integration tests.
The admiration for Excel is sometimes mind-blowing, but it is true. Excel was selected primarily for its mass adoption rate, and the likelihood that testers already use Excel for reporting purposes. Regardless of the test automation solution, it seems reporting naturally finds it way back to Excel.
A library for executing MS Excel based, keyword driven tests with Protractor.