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 (1,926 stars) (118 forks)batch import
good first issuetest

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

Tech stack
csharp
Domain
testing
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
NBomber plugin systemC# unit testingMockingTest framework (xUnit/NUnit)
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine existing test files in the NBomber repository to understand the testing patterns and setup. Review the source code for ReportingSink and WorkerPlugin interfaces to understand their lifecycle. Implement test cases for init, execution, and stop phases, ensuring that an exception from one sink/plugin does not stop others. Use mocking frameworks to simulate failures.