Log current screen after saving a form #5918
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
seadowg
requested changes
Jan 16, 2024
|
|
||
| assertThat(auditLog[2].get("event"), equalTo("form save")) | ||
|
|
||
| assertThat(auditLog[3].get("event"), equalTo("question")) |
There was a problem hiding this comment.
Can you add an assertion on the question paths here (and in the other question events)? I think that'll help readability.
5 tasks
seadowg
approved these changes
Jan 16, 2024
|
Tested with Success! Verified on device with Android 10 Verified cases:
|
|
Tested with Success! Verified on device with Android 13 |
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.
Closes #5915
Why is this the best possible solution? Were any other approaches considered?
Logging the current screen was removed in this pr: #5839 so to fix the issue I've just brought it back.
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
This should just solve the issue. I don't think it's risky since the fix brings back the code that already existed in v2023.3.1 and older versions but it's not the first issue with audits we have discovered recently so there might be more.
Do we need any specific form for testing your changes? If so, please attach one.
No.
Does this change require updates to documentation? If so, please file an issue here and include the link below.
No.
Before submitting this PR, please make sure you have:
./gradlew connectedAndroidTest(or./gradlew testLab) and confirmed all checks still pass