PragmaticFlow/NBomber

[Test] fault tolerance for multiple ReportingSink/WorkerPlugin

Open

#346 opened on May 6, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)CSS (118 forks)batch import
good first issuetest

Repository metrics

Stars
 (1,926 stars)
PR merge metrics
 (Avg merge 11h 10m) (1 merged PR in 30d)

Description

Test Init:

  • test that during TestInit, if some sink throws an exception - it will stop test execution
  • test that during TestInit, if some sink plugin throws an exception - it will stop test execution

Test Execution

  • test if you have multiple ReportingSinks and one failed during work it will not stop others
  • test if you have multiple WorkerPlugins and one failed during work it will not stop others

Test Stop:

  • test that during TestStop, if some sink fail, it will not stop others
  • test that during TestStop, if some plugin fail, it will not stop others

Contributor guide

Research direction
Implement unit tests to verify fault tolerance: during Init, exceptions from a sink or plugin should halt test execution; during Execution, a failure in one sink/plugin should not stop others; during Stop, a failure in one sink/plugin should not stop others. Use mocking to simulate exceptions and assert the expected behavior.
Tech stack
csharp
Domain
testingbackend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#testingNBomber
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70