|
Hi,
Yet another eunit fix: Generate separate surefire XMLs for each test suite Previously the test cases of all test suites (=modules) were put in one and the same surefire report XML thereby breaking the principle of least astonishment and making post analysis harder. Assume the following layout: src/x.erl src/y.erl test/x_tests.erl test/y_tests.erl The results for both x_tests and y_tests were written to only one report grouped under either module x or y (seemingly randomly). Now two reports, one for module x and one for y are generated. This has now been running for a couple of weeks in our system and seems to do the trick. Code here: git fetch git://github.com/klajo/otp.git eunit-surefire-fixes Cheers, Klas _______________________________________________ erlang-patches mailing list [hidden email] http://erlang.org/mailman/listinfo/erlang-patches |
|
On 05/26/2011 06:22 PM, Klas Johansson wrote:
> Hi, > > Yet another eunit fix: > > Generate separate surefire XMLs for each test suite > > Previously the test cases of all test suites (=modules) were put in > one and the same surefire report XML thereby breaking the principle of > least astonishment and making post analysis harder. Assume the > following layout: > > src/x.erl > src/y.erl > test/x_tests.erl > test/y_tests.erl > > The results for both x_tests and y_tests were written to only one > report grouped under either module x or y (seemingly randomly). > > Now two reports, one for module x and one for y are generated. > > This has now been running for a couple of weeks in our system and > seems to do the trick. > > Code here: > > git fetch git://github.com/klajo/otp.git eunit-surefire-fixes > > > > Cheers, > Klas > _______________________________________________ > erlang-patches mailing list > [hidden email] > http://erlang.org/mailman/listinfo/erlang-patches I have included this in 'pu' and it will cook for a while. -- /Henrik Nord Erlang/OTP _______________________________________________ erlang-patches mailing list [hidden email] http://erlang.org/mailman/listinfo/erlang-patches |
|
On Tue, May 31, 2011 at 3:37 PM, Henrik Nord <[hidden email]> wrote:
> On 05/26/2011 06:22 PM, Klas Johansson wrote: >> >> Hi, >> >> Yet another eunit fix: >> >> Generate separate surefire XMLs for each test suite >> >> Previously the test cases of all test suites (=modules) were put in >> one and the same surefire report XML thereby breaking the principle of >> least astonishment and making post analysis harder. Assume the >> following layout: >> >> src/x.erl >> src/y.erl >> test/x_tests.erl >> test/y_tests.erl >> >> The results for both x_tests and y_tests were written to only one >> report grouped under either module x or y (seemingly randomly). >> >> Now two reports, one for module x and one for y are generated. >> >> This has now been running for a couple of weeks in our system and >> seems to do the trick. >> >> Code here: >> >> git fetch git://github.com/klajo/otp.git eunit-surefire-fixes >> >> >> >> Cheers, >> Klas >> _______________________________________________ >> erlang-patches mailing list >> [hidden email] >> http://erlang.org/mailman/listinfo/erlang-patches > > Thank you Klas > > I have included this in 'pu' and it will cook for a while. > > > -- > /Henrik Nord Erlang/OTP Hi, Richard Carlsson commented upon this patch on github a while back, does this mean that the patch will graduate or do you have any further things you'd like to check or perhaps would like me to address? https://github.com/erlang/otp/commit/61621e6623bca4ae75c44a2d8f765098ac798e42 Thanks and Regards, Klas _______________________________________________ erlang-patches mailing list [hidden email] http://erlang.org/mailman/listinfo/erlang-patches |
|
On 07/04/2011 01:14 PM, Klas Johansson wrote:
> On Tue, May 31, 2011 at 3:37 PM, Henrik Nord<[hidden email]> wrote: >> On 05/26/2011 06:22 PM, Klas Johansson wrote: >>> Hi, >>> >>> Yet another eunit fix: >>> >>> Generate separate surefire XMLs for each test suite >>> >>> Previously the test cases of all test suites (=modules) were put in >>> one and the same surefire report XML thereby breaking the principle of >>> least astonishment and making post analysis harder. Assume the >>> following layout: >>> >>> src/x.erl >>> src/y.erl >>> test/x_tests.erl >>> test/y_tests.erl >>> >>> The results for both x_tests and y_tests were written to only one >>> report grouped under either module x or y (seemingly randomly). >>> >>> Now two reports, one for module x and one for y are generated. >>> >>> This has now been running for a couple of weeks in our system and >>> seems to do the trick. >>> >>> Code here: >>> >>> git fetch git://github.com/klajo/otp.git eunit-surefire-fixes >>> >>> >>> >>> Cheers, >>> Klas >>> _______________________________________________ >>> erlang-patches mailing list >>> [hidden email] >>> http://erlang.org/mailman/listinfo/erlang-patches >> Thank you Klas >> >> I have included this in 'pu' and it will cook for a while. >> >> >> -- >> /Henrik Nord Erlang/OTP > Hi, > > Richard Carlsson commented upon this patch on github a while back, > does this mean that the patch will graduate or do you have any further > things you'd like to check or perhaps would like me to address? > > https://github.com/erlang/otp/commit/61621e6623bca4ae75c44a2d8f765098ac798e42 > > Thanks and Regards, > Klas We are now back in motion after the standstill vacation period. and there are alot of patches that will graduate in the coming days. Thank you for the contribution! -- /Henrik Nord Erlang/OTP _______________________________________________ erlang-patches mailing list [hidden email] http://erlang.org/mailman/listinfo/erlang-patches |
| Powered by Nabble | Edit this page |
