Who fixes broken tests? [duplicate]
This question already has answers here: Should a programmer fix someone else’s failed build? [closed] (16 answers) Closed 11 years ago. Our small team has made the curious observation that diagnosing and fixing broken automated tests is a useful activity; in particular, if the CI build indicates that developer A’s last check-in broke some tests, […]
Continuous integration and modifying existing UI automation tests
Our team is currently facing a situation where we are changing a feature that is in the product today. This feature has Selenium automation tests associated with it.
Continuous integration and modifying existing UI automation tests
Our team is currently facing a situation where we are changing a feature that is in the product today. This feature has Selenium automation tests associated with it.
Continuous integration and modifying existing UI automation tests
Our team is currently facing a situation where we are changing a feature that is in the product today. This feature has Selenium automation tests associated with it.
Continuous integration and modifying existing UI automation tests
Our team is currently facing a situation where we are changing a feature that is in the product today. This feature has Selenium automation tests associated with it.
How do I set up pairing email addresses?
Our team uses the Ruby gem hitch to manage pairing. You set it up with a group email address (e.g. [email protected]) and then tell it who is pairing:
How do I set up pairing email addresses?
Our team uses the Ruby gem hitch to manage pairing. You set it up with a group email address (e.g. [email protected]) and then tell it who is pairing:
How do I set up pairing email addresses?
Our team uses the Ruby gem hitch to manage pairing. You set it up with a group email address (e.g. [email protected]) and then tell it who is pairing:
How do I set up pairing email addresses?
Our team uses the Ruby gem hitch to manage pairing. You set it up with a group email address (e.g. [email protected]) and then tell it who is pairing:
Are “Compile to JavaScript” Frameworks Hostile to Continuous Integration?
Lately we’ve been looking at ways to improve automated testing and related tooling of our enterprise-level GWT web app. I’ve realized that in some ways, GWT is a bit hostile to automated testing, mainly because of the nature of the long GWT compile times from Java to JS. This makes unit testing somewhat challenging, but it also puts some roadblocks up for testing in a CI environment. I’ve also found out that some of our build and deployment processes are somewhat complicated due to the nature of GWT’s compile process.