Skip to content

Export retries from instrumentation test logs#13095

Draft
samer-stripe wants to merge 1 commit into
masterfrom
samer/instrumentation-test-retry-data
Draft

Export retries from instrumentation test logs#13095
samer-stripe wants to merge 1 commit into
masterfrom
samer/instrumentation-test-retry-data

Conversation

@samer-stripe

@samer-stripe samer-stripe commented May 13, 2026

Copy link
Copy Markdown
Collaborator

Summary

Export retries from instrumentation test logs and display them in JUnit reports for Bitrise to understand.

Motivation

Better Bitrise reporting

Testing

  • Added tests
  • Modified tests
  • Manually verified

@samer-stripe samer-stripe force-pushed the samer/instrumentation-test-retry-data branch from 97fcee0 to 934e896 Compare May 13, 2026 14:52
@samer-stripe samer-stripe force-pushed the samer/instrumentation-test-retry-data branch 2 times, most recently from c5a6785 to 9e44487 Compare May 13, 2026 16:02
]
}
expanded
}

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't the most ideal way for doing this but many of the other Android instrumentation runners available in open-source have a mix of low maintenance, high complexity, and incompatibility with JUnit rules

mkp.yield(row.logLine.toString())
}
}
}

@samer-stripe samer-stripe May 13, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The synthetic test cases that are pulled out from the logcat files don't have full logs, only when the logged retry rule. The successful or last failure test case will have full logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant