Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explicit exception to abort the scan process #53

Open
5 tasks
obfischer opened this issue Aug 14, 2020 · 0 comments
Open
5 tasks

Explicit exception to abort the scan process #53

obfischer opened this issue Aug 14, 2020 · 0 comments
Labels
status:team discussion The team needs to discuss how to deal with the issue's request topic:architecture This issue mainly focuses or has impact on the performance of jQA

Comments

@obfischer
Copy link
Contributor

Feature Descripion

As contributor to jQA,
would like to a have a dedicated exception available, which can be used programmatically to abort the scan process of any ressource,
to that we can use this exception to signal that the process of scanning a ressource has failed.

Addtional information on the requested Feature

This would help us to differentiate between failure situations, which already has been handled and unhandled failure situations

Definition of Done for the Implementers

  • Unittests have been written
  • Integration tests have been written
  • Test coverage is the same or even better then before
  • Documentation has been written
  • Added a note on the new feature to the release notes
@obfischer obfischer added status:team discussion The team needs to discuss how to deal with the issue's request topic:architecture This issue mainly focuses or has impact on the performance of jQA labels Aug 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:team discussion The team needs to discuss how to deal with the issue's request topic:architecture This issue mainly focuses or has impact on the performance of jQA
Projects
None yet
Development

No branches or pull requests

1 participant