Say hello to JIRA Agile and JIRA Capture Learn More »

Archives for the tag: automated testing

Hello again! Glad to see you've come back for more tips on making Bamboo awesome for Git and Hg teams. Today we'll talk all about tests. Grab a chocolate and get comfortable. Comparing test status against upstream When we left off last time, we were talking about slick ways to manage merges to upstream branches. Here's another scenario: let's assume that in your team sometimes a bad code hits the upstream. For example people do commit small fixes directly to the upstream branch. Or there is necessity

Continue reading »

Making releases a "non-event" is one of the goals many teams aspire to when they adopt agile development practices.  That might mean releasing several times daily, or (more likely) at the end of each iteration. Either way, most teams eventually normalize on some flavor of continuous delivery. A common flavor is to build the code and deploy it to a test environment several times a day, then pause at that point in the pipeline.  Every few days (or weeks), you look through the builds that passed all

Continue reading »

Clover Goes Mobile!

The Android market is rapidly increasing, being one of the most popular platforms, not only for customers, but also as a platform for developers to create their apps. Just few numbers: Google Play just hit 25 billion downloads in total (15 billion downloads in the last year) over 670,000 applications available on Google Play over 100'000 registered developers on Google Play over 500 million activations of Android devices, 1.3 million being added every day Taking into account this rapidly

Continue reading »

Asynchronous Build Tiers for Faster Feedback

"Asynchronous Build Tiers"... could I possibly think of a dryer, technical-for-the-sake-of-sounding-technical term for what I'm about to describe? Geez. I'm almost embarrassed. It's actually an exciting concept, though. Let's say your team commits code changes Chicago-style (early & often). Let's also say that you have several layers of automated tests: unit tests, integration/API level tests, and UI-based tests that, in total, take a couple hours to run. Rather than making your devs wait

Continue reading »