Using mabot and RIDE effectively

[Pedro Perez]

Hey guys,

We are adopting Robot Framework and so far so good. However some of our test cases are manual test cases---they have undefined keywords so far--as business requirements force us to speed up projects and we don't get time to make sure every test case actually passes.

We have a need to report on test cases while they're manual and show which ones pass and fail. I understand the mabot tool can handle this quite well, and indeed after playing with it for some time it appears to fit just this need.

However, when I mark tests as "PASS" or "FAIL" with mabot, and hit save, it doesn't seem to actually alter the file at all--opening these tests in RIDE later do not reflect any changes, and indeed opening these tests in mabot later do not reflect any changes--I must start over marking things as PASS/FAIL. I am opening *.txt files with both RIDE and Mabot.

How are other people using these tools together? Currently we can zip through RIDE no problem, but I'm wondering if the accepted practice is something like:

1. Make test cases in RIDE

2. Once finished making test cases, use Mabot to work through them and say which are PASS/FAIL

3. Save that result somehow (doesn't seem to be working for me in Mabot currently, perhaps I am doing it wrong however)

Ideally we would simply get our RIDE test cases all passing, but sadly some tests must remain manual for now due to time constraints.

BONUS QUESTION

Is there a way to mark a test case in RIDE such that RF won't execute it? that is, tell RF that this test case is manual and to ignore it (I suppose you could do that simply with tags).

Thanks everyone!

Cheers

Pedro

[Dezider Mesko]

-e, --exclude <tag>
	Selects the test cases by tag.

http://robotframework.googlecode.com/svn/tags/robotframework-2.5.5/doc/userguide/RobotFrameworkUserGuide.html#all-command-line-options

d.

Pedro

--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-u...@googlegroups.com.
To post to this group, send email to robotframe...@googlegroups.com.
Visit this group at http://groups.google.com/group/robotframework-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Tatu aalto]

Ugh

The test suite/case result is not saved in the test suite files, by mabot or by robot framework. Result, in case of mabot is saved in output.xml file (just like RF would do). The mabot user guide gives better explanation of the mabot features [1].

-Tatu
[1] http://code.google.com/p/robotframework-mabot/wiki/UserGuide

[Pedro Perez]

"Ugh."

It does save much better to XML. You CAN open a test suite file (.txt) with Mabot, and it DOES present the save option at that point, but the save option does nothing. It's better to either "Save As" to generate a new XML file or like you said open the output.xml file in Mabot. 

Still though, is the "accepted" practice to write a bunch of test cases with RIDE, run them and expect your manual test cases to fail, and then use Mabot to work through the manual test cases, setting them to PASS as you go through them?

To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-users+unsub...@googlegroups.com.

To post to this group, send email to robotframe...@googlegroups.com.
Visit this group at http://groups.google.com/group/robotframework-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-users+unsub...@googlegroups.com.

[Tatu Aalto]

Ugh

1) I have always used "Save As" because I want to know where and what name the xml files goes.

2) Yes, I write all my test with Ride. I usually tag the automated/manual test with different tags and use the tag to select correct test to only run automated test [1] from command line (it helps to eliminate false negatives). Then I generate different output.xml file with mabot from the manual test. For last I combine both output.xml files rebot [2] to have unified test report.

I use tags quite a lot, mainly to select correct test when I run them from a command line, usually assisted with a script.

-Tatu

[1] http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html?r=2.7.7#selecting-test-cases
[2] http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html?r=2.7.7#combining-outputs

To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-u...@googlegroups.com.