Add E2E tests for crash loop scenarios #1181
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
twometresteve
approved these changes
Mar 10, 2021
...arios-bugsnag/src/main/java/com/bugsnag/android/mazerunner/scenarios/CXXCrashLoopScenario.kt
Show resolved
Hide resolved
features/full_tests/batch_1/identifying_crashes_on_launch.feature
Outdated
Show resolved
Hide resolved
...jvm-scenarios/src/main/java/com/bugsnag/android/mazerunner/scenarios/JvmCrashLoopScenario.kt
Outdated
Show resolved
Hide resolved
features/full_tests/batch_1/identifying_crashes_on_launch.feature
Outdated
Show resolved
Hide resolved
fractalwrench
force-pushed
the
PLAT-5979/crash-loop-tests
branch
from
f9b6a7d to
d904466
Compare
fractalwrench
force-pushed
the
PLAT-5979/crash-loop-tests
branch
from
d904466 to
eb97cbd
Compare
fractalwrench
merged commit 47fc52a
into
integration/road-1175-identify-crashes-on-launch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Goal
Adds E2E scenarios where Bugsnag allows an application to recover from a crash loop by checking the value of
Bugsnag.getLastRunInfo(). Along with #1180 this adds the required E2E test coverage for the project.Changeset
Bugsnag.getLastRunInfo().crashedDuringLaunchis true, the application enables a 'safe-mode' which avoids the crashy pathLastRunInfoare populated as expected.Note: the NDK
LastRunInfofunctionality hasn't been implemented yet so the scenario fails. This will be addressed in PLAT-5978 which will uncomment the E2E test.