damphyr / rutema Goto Github PK

Currently in Rutema, the suite setup and teardowns are treated as normal test cases. This includes problems such as the "test setup" and "test teardown" being run before and after the "suite setup". In addition these are treated by the reporter as additional "test cases", which can only confuse the test user.

Even without a "suite setup" or "suite teardown", the reporter will still report 2 tests executed, presumably tr eating the "test setup" as an additional test case.

When a test is not marked by "is_special", then exceptions thrown from parsing rutema elements invovled in the test do not appear in the reporting output in useful manner.

This appears to be due to line 77 in engine.rb.

Perhaps the actual problem lies by the error reporting itself.

I am reasonably sure, you can replicate this problem by adding a basic ruby error into a parser rutema extension element.

Happens on 2.0.0.pre7

Some way to display just the failed test (or eventually some keyword to search for, and jumping quick to the failed test) in rutema_web

After updating to Ruby 2.3.1 (also tested with 2.3.3.), I found that the configuration file name parsed from the command line, becomes corrupt, after the call on line 205 in configuration.rb to evaluate the ruby content.

If I change the filename argument to FILE everything work. Otherwise, the string becomes corrupted and rutema breaks.

In the web GUI add a summary at the top of each Run page