Skip to content

Issue/13326 ignore threat usecase#13767

Merged
ashiagr merged 4 commits intodevelopfrom
issue/13326-ignore-threat-usecase
Jan 15, 2021
Merged

Issue/13326 ignore threat usecase#13767
ashiagr merged 4 commits intodevelopfrom
issue/13326-ignore-threat-usecase

Conversation

@ashiagr
Copy link
Copy Markdown
Contributor

@ashiagr ashiagr commented Jan 14, 2021

Parent #13768

This PR adds ignore threat use case.

To test:
That IgnoreThreatUseCaseTest tests run fine and cover action results.

PR submission checklist:

  • I have considered adding unit tests where possible.
  • I have considered adding accessibility improvements for my changes.
  • I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

@ashiagr ashiagr added this to the 16.6 milestone Jan 14, 2021
@ashiagr ashiagr self-assigned this Jan 14, 2021
@peril-wordpress-mobile
Copy link
Copy Markdown

peril-wordpress-mobile bot commented Jan 14, 2021

You can trigger optional UI/connected tests for these changes by visiting CircleCI here.

@peril-wordpress-mobile
Copy link
Copy Markdown

peril-wordpress-mobile bot commented Jan 14, 2021

You can test the changes on this Pull Request by downloading the APK here.

@ashiagr ashiagr mentioned this pull request Jan 14, 2021
3 tasks
@ashiagr ashiagr requested a review from ParaskP7 January 14, 2021 09:52
Copy link
Copy Markdown
Contributor

@ParaskP7 ParaskP7 left a comment

Choose a reason for hiding this comment

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

👋 @ashiagr !

I have reviewed and tested this PR as per the instructions. All looks good to me, nice work, especially with the tests! 🌟

I have only minor test related comment(s). I am going to approve this PR but give you the change to apply any comments before merging this to develop. Feel free to merge it as is if you like.

PS: What would you say if we added a test for the GetThreadModelUseCase? I know this use case is very simple, as it will only verify that the scanStore is triggered, but even that is a valid test IMHO and can help setting up the testing structure so that when in the future this become more complicated the test a) might fail and b) be easier to enhance (since the test suite is already available). Wdyt?

@ashiagr
Copy link
Copy Markdown
Contributor Author

ashiagr commented Jan 15, 2021

Thanks for the review @ParaskP7! You always come up with thoughtful suggestions!

PS: What would you say if we added a test for the GetThreadModelUseCase? I know this use case is very simple, as it will only verify that the scanStore is triggered, but even that is a valid test IMHO and can help setting up the testing structure so that when in the future this become more complicated the test a) might fail and b) be easier to enhance (since the test suite is already available). Wdyt?

Added to the backlog, will surely consider adding it, thank you!

@ParaskP7
Copy link
Copy Markdown
Contributor

Thanks for the review @ParaskP7! You always come up with thoughtful suggestions!

You are very kind @ashiagr ! Thank you for considering my suggestions. 🤗 PS: When you find yourself under the clock, feel free to skip any of those. My intention is mainly discussing the subject, whether that is applied or not afterwards is secondary to me.

Added to the backlog, will surely consider adding it, thank you!

Thank YOU! ❤️

@ashiagr ashiagr merged commit 03e9662 into develop Jan 15, 2021
@ashiagr ashiagr deleted the issue/13326-ignore-threat-usecase branch January 15, 2021 08:40
@ParaskP7 ParaskP7 self-assigned this Jan 15, 2021
@ashiagr ashiagr mentioned this pull request Jan 18, 2021
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants