You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I request to add a feature for console application to have a new type output which combines output and result files into single file. The reason is that our tests produces huge amount of logs (due complexity nature) and once it is failing we need to find test start time in results file, then search for this time in the output files. This is extra effort considering that output files in some cases reaches 230 MB and more file size of output and tests running up to 8 hours (nightly) with 800 tests.
Currently we are having hard times to find failure times with messages and trying forcibly to inject failure information into output file which results in changes for each test if running based on standard Nunit structure. We do have our dynamically loading test and this makes easier to reach this goal.
The combined file must have fallowing entries:
All output file content
A clear test start entry with test name and full class name of the test
Test Setup and Teardown entries
Test end which includes fallowing information:
test outcome (success/failed/ignored/inconclusive);
full failure message including stack traces (must include multiple stack traces for Assert.Multiple case);
total number of run so far tests;
total number of failed tests so far
total number of ignored tests
Duration time which took to execute the unit test (exclusion for ignored)
Ignore message if the test was ignored
All entries should be fallowed based on execution time. The question only stands for tests running in parallel since my guess all this information cannot be mixed up for multiple tests. Thus I would expect logging output by blocks to have a separation between tests.
Example of preliminary new file combined content file:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
==== Test Name: My test name for checking Assert.Muliple functionality ====
==== Test Class: MyFileName.MyTests.AssertTests.TestAssertMultiple ====
.... (output file content)
==== ONETIME SETUP ====
.... (output file content)
==== ONETIME SETUP END ====
==== SETUP ====
.... (output file content)
==== SETUP END ====
==== EXECUTING ====
.... (output file content)
.... (test result failure information including stacktrace if failed)
.... (output file content)
==== EXECUTION END ====
==== TEARDOWN ====
.... (output file content)
==== TEARDOWN END ====
Test Name: My test name for checking Assert.Muliple functionality
Result: Failed
[Ignore message: A bug #1192 created due it Assert.Multiple does not work]
Test Count: 3383, Passed: 3371, Failed: 2, Warnings: 0, Inconclusive: 0, Skipped: 10
Skipped Tests - Ignored: 10, Explicit: 0, Other: 0
Start time: 2022-07-01 06:24:10Z
End time: 2022-07-01 06:26:54Z
Duration: 163.630 seconds
++++++++++++++++++++++++++++++++ END OF TEST ++++++++++++++++++++++++
This discussion was converted from issue #1199 on December 14, 2024 16:21.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I request to add a feature for console application to have a new type output which combines output and result files into single file. The reason is that our tests produces huge amount of logs (due complexity nature) and once it is failing we need to find test start time in results file, then search for this time in the output files. This is extra effort considering that output files in some cases reaches 230 MB and more file size of output and tests running up to 8 hours (nightly) with 800 tests.
Currently we are having hard times to find failure times with messages and trying forcibly to inject failure information into output file which results in changes for each test if running based on standard Nunit structure. We do have our dynamically loading test and this makes easier to reach this goal.
The combined file must have fallowing entries:
All entries should be fallowed based on execution time. The question only stands for tests running in parallel since my guess all this information cannot be mixed up for multiple tests. Thus I would expect logging output by blocks to have a separation between tests.
This is fallow up from work item #1192.
Example of preliminary new file combined content file:
Beta Was this translation helpful? Give feedback.
All reactions