PragmaticFlow/NBomber

[Test] fault tolerance for multiple ReportingSink/WorkerPlugin

Open

#346 建立於 2021年5月6日

在 GitHub 查看
 (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
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
NBomber plugin systemC# unit testingMockingTest framework (xUnit/NUnit)
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
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.