4 ms·
I'm open sourcing a Java Selenium library with page performance assertions built in as part of my startup. It will let you do things like: test.config.setSL
by ericb 10y ago
I'm open sourcing a Java Selenium library with page performance assertions built in as part of my startup. It will let you do things like:
test.config.setSLAMaxTime(2000); // set time in MS
assertSLAMet(); // add this to any page
It will also allow you to assert specific URL's, and window timings. You can then use these assertions to pass/fail builds. I also have some other nifty ideas on preventing performance regressions I'm building into this (smart benchmarking vs. previous).
If anyone is interested, I'll be announcing it here when we open source it:
http://signup.browserup.com/ http://signup.browserup.com/
- orf 10y ago> What if your Selenium tests had performance asserts for CI/CD Isn't this just... a single function? Like, how the heck do you build a startup around that. We do this as part of our Python selenium tests, I didn't realize it wasn't built in to be honest.
- ericb 10y agoThere's a lot more to it--this is just a tiny part we're giving away, not something we'll make money on. We do real-browser load testing in the cloud using the same scripts folks use for integration testing. Because they can also run locally, you can run them alongside your integration tests with each commit, and you always know you have working scripts. Scripts are easy to code and maintain because they can use page objects like functional tests. This means you can have versioned load test/monitoring scripts in your project that always work with a particular sha. When you deploy, you can start transactional monitoring immediately. It also means load testing is not a separate stage in your development lifecycle.