I'm testing minitest-reporters and found something, that when it is used with the "parallelize_me!" option the result output with "SpecReporter" is hard to read, because it shows the currently running test_case Class, but so others test cases finish it overlaps with the other Class, so you get an output that seems that the test_cases are from a class that they are not
that gets me think that maybe there's a way to hide the class of the currently running test_case
I believe most reporters were not supposed to be used with "parallelize_me!" :worried:
I'm open for suggestion on how SpecReporter should work in this case (or PR's ;) )
I think the best way will be to hide the "currently launching" name of the parent Class of the test case, and only show the lines with the PASS or ERROR test cases results. That way one can name the test case with a naming scheme like "test_suite1_user_login" or "test_user_login_suite1" and you look at the output that shows only the name and result of the test cases and not showing the parent Class or suite name where the test case belongs.
that way you only get the output of the results of the test cases as they are finishing... the output of the Class or suite makes sense if they run one by one, but with parallelize option it only makes the output difficult to understand
Well, perhaps it would be better to fallback to another reporter if "parallelize_me!" was called. Imho, SpecReporter is supposed to work in non-parallelized situation only.
can i able to edit my minitest html test report after it has been generated?
is there any possibility to do that?
Hi. I'm going to send a Pull Request. Before I must be sure that after my changes all tests are green. But I found only 2 test classes: test/integration/reporters/junit_reporter_test.rb and MinitestReportersTest. Miss I something or there are not so many tests in this project?
There not so many tests :( more than two, but perhaps not all of them are related to the changes you are going to do. Also it is a good idea to run gallery (it runs some specific test with all reporters)
ah crap, this community seems dead :(
Hi, as you may have already known Rails 6 supports parallel test execution. Bad news is that minitest-reporters is not ready for this. I spent some time investigating it and the only problem I see is communication between workers (in case of process-based Parallelism). I need to store list of already started test-cases (see method BaseReporter#before_test) but with process-based Parallelism every worker has its own array of started test-cases. Any ideas?