SE-PRG/azmitool

unit testing - step 2

Open

#151 opened on May 16, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (5 forks)auto 404
exceptions-handlinggood first issuetesting

Repository metrics

Stars
 (2 stars)
PR merge metrics
 (PR metrics pending)

Description

This is continuing from issue #135 and PR #149

Next tasks in unit testing:

  • Add negative tests where possible
  • Add mock for GetToken in IDCheck tests
  • fix other TODO: issues
  • merge similar tests into Theory
  • align test cases according to AAA approach (arrange-act-assert) (three lines of code)
  • add more descriptive test names (see comment in PR #149 )

Pipeline related tasks

  • Confirm pipeline is integrated as PR validation
  • re-check code coverage in pipeline

Contributor guide

Research direction
Examine the existing unit tests in the project. Follow the checklist: add negative tests, mock the GetToken method in IDCheck tests, merge similar tests into Theory, align tests to AAA pattern, and improve test names. Start by understanding the current test structure and xUnit conventions.
Tech stack
csharpazure
Domain
backendsecurity
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#Unit testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70