As I'm running upgrades in #463, I'm finding lots of jsTestDriver.conf files, which are dead. For now, I'll just list the packages that I'm touching, that have browser tests here:
samsam
buster-test
referee
evented-logger
buster-html-doc
buster (see run-integration-tests - hacked up phantom runner for now)
For me, the easiest way to get at least some tests to run automatically is to use grunt-buster + phantom, so I'll add that where I can. Later, I'll try to get that to work with buster-ci and/or saucelabs/browserstack, but for now I just want to go through as many packages as possible an get them up to date, while picking up some knowledge, so grunt will have to do.
The following modules also use something related to phantom for their testing:
buster-server-cli
ramp
The following could use integration tests in the browser:
dominykas
commented
6 years ago
As I'm running upgrades in #463, I'm finding lots of jsTestDriver.conf files, which are dead. For now, I'll just list the packages that I'm touching, that have browser tests here:
samsambuster-testrefereeevented-loggerbuster-html-docbuster(seerun-integration-tests- hacked up phantom runner for now)For me, the easiest way to get at least some tests to run automatically is to use
grunt-buster+ phantom, so I'll add that where I can. Later, I'll try to get that to work withbuster-ciand/or saucelabs/browserstack, but for now I just want to go through as many packages as possible an get them up to date, while picking up some knowledge, so grunt will have to do.The following modules also use something related to phantom for their testing:
buster-server-clirampThe following could use integration tests in the browser:
buster-static