Project: saikrishna321/AppiumTestDistribution


This report was generated at 2018-08-16 19:50:58 UTC. We have analyzed the CI history of your project from your Travis-CI build logs and your GitHub repository and have checked several dimensions of your CI process to find deviations from accepted best practices. In the following, you will find the results of our analysis.

We would highly appreciate your feedback and constructive comments on this report. This helps us to evaluate the idea and to further improve the report in the future. Please consider taking the following quick survey


Slow builds

Build times can increase due to high workload of the build server or due to increased project complexity over time. In fact, slow-down is often hard to detect, because it slowly creeps into the project. A slow build causes wait times for developers, adds a large overhead to the whole process, and should be avoided. Our summary provides an overview over recent build times and reports recent cases, in which the build duration takes substantially longer than usual.


↗ Uptrend -

During the last 90 days, your build duration increased by 22.35%




Possible problems found in recent builds on your branches:

Severity Branch Date Build Duration Description
Medium master 2018-08-04 15:12:30 412053326 37.37 minutes This build is slower than 89.71% of your builds on master
Medium ReportPortal 2018-08-04 15:23:43 412053310 35.92 minutes This build is slower than 85.29% of your builds on master
Medium chromedriver 2018-05-24 09:27:00 383097179 1.01 hours This build is slower than 100.00% of your builds on master


Broken release branch

The CI pipeline requires a working build to properly assess whether changes introduce a problem, so recovering the build is the highest team priority. A build on the release branch typically also involves the deployment of the build results and should never fail. Our summary provides an overview over the number of recent release-branch failures and indicates the trend over time.


↘ Downtrend -

Downtrend: during the last 90 days, the number of broken release builds decreased by 35.77%




During the last 90 days your master was broken 62 times. On average, it took you 1.94 weeks to fix it again.



Skip failed tests

Having an elaborated test-suite is one of the pillars of continuous integration. It provides protection from invalid changes and failing tests have to be taken seriously. Deleting or skipping a failing test might fix a broken build, but it is a removal of the symptom rather than a fix of the root cause and should be avoided.


No skip test warnings found!



Late merging

Benefits of CI diminish, when individual feature branches are synchronized sparsely or when they are too long-lived. We point out several scenarios in our reports that might indicate such a ‘Late Merging’


Issues found for branch: CI
Severity Description
High In your project, branches are typically synced with master every 9.27 hours. However, branch CI has last synced with master on 2018-02-27 06:12:33, and branch chromedriver has commits that are 9.88 weeks newer than that.
High Your latest commits were performed on branch ReportPortal on 2018-08-04 15:23:43. However, your last changes on branch CI happened 22.6 weeks ago, and have not been merged yet. In your project, you typically merge branches within 7.62 weeks.
High In your project, branches do not deviate for more than 8.51 weeks. However, you are working on branch CI since 13680670s (~22.62 weeks) without synchronization.

Issues found for branch: chromedriver
Severity Description
High You have been working on chromedriver for 3.88 weeks.Your feature branches are typically open for 9.27 hours.

Issues found for branch: fix-309
Severity Description
High In your project, branches are typically synced with master every 9.27 hours. However, branch fix-309 has last synced with master on 2018-03-23 08:08:33, and branch chromedriver has commits that are 6.44 weeks newer than that.
High Your latest commits were performed on branch ReportPortal on 2018-08-04 15:23:43. However, your last changes on branch fix-309 happened 19.19 weeks ago, and have not been merged yet. In your project, you typically merge branches within 7.62 weeks.
Medium In your project, branches do not deviate for more than 8.51 weeks. However, you are working on branch fix-309 since 11600110s (~19.18 weeks) without synchronization.

Issues found for branch: mongo
Severity Description
High You have been working on mongo for 2 weeks.Your feature branches are typically open for 9.27 hours.

Issues found for branch: pushAppToRemote
Severity Description
High In your project, branches are typically synced with master every 9.27 hours. However, branch pushAppToRemote has last synced with master on 2018-02-23 13:34:50, and branch chromedriver has commits that are 10.41 weeks newer than that.
High Your latest commits were performed on branch ReportPortal on 2018-08-04 15:23:43. However, your last changes on branch pushAppToRemote happened 23.15 weeks ago, and have not been merged yet. In your project, you typically merge branches within 7.62 weeks.
High In your project, branches do not deviate for more than 8.51 weeks. However, you are working on branch pushAppToRemote since 13999733s (~23.15 weeks) without synchronization.

Show more…

Tip: Frequently synchronized branches are easier to integrate.
Tip: Break features into smaller tasks to finish them faster.

Thanks for reading the summary! Please now fill our quick survey