Improve Confidence when Deploying about tutor-js HOT 5 CLOSED

I like the approach you've setup in #924 (Selenium + coveralls)

How hard is it to spec network requests with Selenium? Some light googling suggests its possible but I've not personally done that before.

I'm think it would be great if we could test "When this input sequence is conducted, a http PUT matching XXX is issued" Selenium gives us the ability to craft the input sequences, but I'm not sure how to spec the network request.

from tutor-js.

Technically, it doesn't...by design. Hackishly you can form the same requests against the running selenium server.

from tutor-js.

Yep, "recording" the requests would be a quick way to create the mock JSON for tests and could be easily updated. Ruby uses vcr/vcr (readme has a list of ports) and I found linkedin/sepia for NodeJS.

For browsers, I created sepia.js a while back to play back cassettes for octokat.js but with some of the recordo code it could record the requests too.

from tutor-js.

From the discussion on selecting things via classes, data- attributes, or :nth-of-type(): from an accessibility angle, would it make sense to default to aria- attributes when selecting things in Selenium?

Of course, those attributes are probably not enough to do things but it would be easier than having entirely separate helpers that navigate through the UI.

Adding accessibility is one of the items for this semester so we'll probably start having tests for it too 😄

from tutor-js.

I think we've done most of the items in this except for using fixtures files. Those could be added with something like https://github.com/philschatz/sepia.js (mentioned above) /cc @nathanstitt since he mentioned the VCR stuff

from tutor-js.