Updates:
Status: Pending
Comment #1 on issue 1687 by pekka.klarck: Support more general merging
results with Rebot
http://code.google.com/p/robotframework/issues/detail?id=1687
Your use case looks totally valid. You are also correct that --rerunmerge
doesn't work here. It was designed to handle only a certain merge
operation, not to be a generic merger. Adding more merge possibilities is
definitely possible as long as they are generic and have somewhat clean
usage/semantics.
If I got it right, in your situation tests in merged outputs should be
placed into the suite in the original output into corresponding places. In
general that is easy, but there are at least the following questions to be
answered:
1) What to do if there already exists a test with same name? Merge them
like with --rerunmerge, add new test anyway (there shouldn't be technical
restrictions for this), or give an error?
2) What to do a test in merged output has no corresponding suite? Should we
copy the whole suite from the merged output or should this be an error?
3) If we allow adding also missing suites (see above), what should we do if
the top level suites are different?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "robotframework-commit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to robotframework-commit+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
