[Test] fault tolerance for multiple ReportingSink/WorkerPlugin · PragmaticFlow/NBomber#346

2021-05-06T10:43:34.000Z

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

(0 评论) (0 反应) (0 负责人)CSS (1,926 star) (118 fork)batch import

good first issuetest

描述

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

贡献者指南

技术栈: csharp
领域: testing
议题类型: test
难度: 3
预计时间: 1-2 days
活动状态: stale
清晰度: clear
前置要求: NBomber plugin systemC# unit testingMockingTest framework (xUnit/NUnit)
新手友好度: 60
研究方向: 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.