We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The actions package classes, specifically the BlobRemoveAction class, currently lack unit tests.
actions
BlobRemoveAction
Here's a brief outline of what the tests for BlobRemoveAction could cover:
Instantiation: Test that the BlobRemoveAction class can be instantiated correctly, and that all initial values are set as expected.
Method functionality: For each method in the BlobRemoveAction class, write tests that confirm the method works as expected under normal conditions.
Edge cases: Consider edge cases and write tests for them. For example, what happens if we pass null or unexpected values to the methods?
Error handling: Test that the class handles errors gracefully and as expected.
The text was updated successfully, but these errors were encountered:
kerbymart
No branches or pull requests
The
actions
package classes, specifically theBlobRemoveAction
class, currently lack unit tests.Here's a brief outline of what the tests for
BlobRemoveAction
could cover:Instantiation: Test that the
BlobRemoveAction
class can be instantiated correctly, and that all initial values are set as expected.Method functionality: For each method in the
BlobRemoveAction
class, write tests that confirm the method works as expected under normal conditions.Edge cases: Consider edge cases and write tests for them. For example, what happens if we pass null or unexpected values to the methods?
Error handling: Test that the class handles errors gracefully and as expected.
The text was updated successfully, but these errors were encountered: