corvus-dotnet / corvus-dotnet/Corvus.Tenancy

Add specs for common failure cases

Open
#93 0 comments 0 reactions 0 assignees View on GitHub
IMM
Dominant language
C#
Stars
6
Forks
1
PR merge metrics
No merged PRs in 30d

Description

We don't have all the specs required to get the IMM point for 'Specs which cover common failure cases'

Specs for `Corvus.Tenancy.Storage.Azure.Blob` do include two failure cases, but there are issues including (but not necessarily limited to):

* you wouldn't know from the Scenario titles that these test failure cases
* no test for failure when trying to create a child under a non-existent parent
* no test for failure when trying to update a non-existent child
* no test for failure when trying to delete a non-existent child
* no test for failure when trying to get children of a non-existent child
* no test for whether errors caused by misconfiguration are intelligible

There are no specs for failure at all for the Cosmos, Gremlin, and Azure Storage tenanted storage providers.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the existing specs for Corvus.Tenancy.Storage.Azure.Blob and the specs for the Cosmos, Gremlin, and Azure Storage tenanted providers. Review the current failure-case scenarios, then add coverage for the listed missing failures and for intelligible misconfiguration errors. Done means the common failure cases are covered with scenario titles that clearly identify failures.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp
Domain
testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.