Skip to content
This repository has been archived by the owner on Jun 28, 2024. It is now read-only.

Releases: shazam/fork

3.16.0

25 Aug 14:53
Compare
Choose a tag to compare
  • ddmlib updated to 30.2.2
  • Improve screen recording of failed tests

3.15.0

14 Apr 10:58
Compare
Choose a tag to compare
  • Added support for Android Gradle plugin 7.1.3

3.14.0

14 Apr 07:52
Compare
Choose a tag to compare
  • Added support for Android Gradle plugin 7.0.x
  • Added support for Gradle 7.0

3.5.0

17 Aug 15:25
Compare
Choose a tag to compare
Release 3.5.0

1.3.0

14 Apr 17:20
Compare
Choose a tag to compare

This release is intended to allow some grade of flakiness in the tests, giving the possibility to retry failing tests during the same session.
This allows failed test cases to be re-executed in the same pool.

There are two possibile configuration params:

--total-allowed-retry-quota  (Default = 0)  This is the total amount of allowed retries. 
                                            If a test case fails and this quota hasn't been exhausted yet, 
                                            the test case is scheduled to be executed again in the same device pool. 
--retry-per-test-case-quota  (Default = 1)  This is the amount of times a single test can be re-executed
                                            before declaring it a failure.

Or in the gradle extension:

fork {
    totalAllowedRetryQuota = 2
    retryPerTestCaseQuota = 1 
}

Example of test executed multiple times, before it passed:

The detail of a failed test that is executed again (and then passes) has now a yellow icon/color:
android-jenkins_uk_shazamteam_net_8080_job_android-master-integration_1604_fork_report_


Example of flakiness report, with tests re-executed.

android-jenkins_uk_shazamteam_net_8080_job_android-ongoing-flakiness_546_fork_flakiness_report_


Example of output log:

INFO Test demotest.MyClassTest#justATest enqueued again into pool:all=sw0-up