StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POrspec: how can I continue test after first failure
primarykey
Id
18828790
data
AcceptedAnswerId
0
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-16T13:04:53.100
FavoriteCount
0
LastActivityDate
2013-09-16T14:44:03.570
LastEditDate
2013-09-16T13:09:59.280
LastEditorUserId
233087
OwnerUserId
233087
ParentId
0
PostTypeId
1
Score
4
ViewCount
1235
LastEditorDisplayName
text
Body
I am using rspec to system test a device. The device is modular so that any number of sub-devices may be connected to a test rig. There are many places where I want to write tests that will loop over the connected of sub-devices and run the same test on each device. Basically, this is what I am trying to do: <pre><code>before(:all) @tool = discover_sub_devices() @tool.sub_devices.should == exp_sub_device_list end describe "some sub device tests" do @tool.sub_devices.each do |dev| it "should succeed at doing things" do dev.do_thing.should == success end end end </code></pre> Unfortunately this does not work. I get errors saying @tool is nill and does not contain a class <code>sub_devices</code> before the tests even run. So the tests are being parsed before the <code>before(:all)</code> block runs. One way I can make it work is by putting the loop inside of the <code>it</code> block. Like this: <pre><code>it "should succeed at doing things" do @tool.sub_devices.each do |dev| dev.do_thing.should == success end end </code></pre> The problem with doing it this way is that I really want to test all the sub-devices even if the first one fails. I want to see a report of exactly how many sub devices had failures. This code will break out as soon as one fails and not test the rest. I realize this is probably not a normal use case for rspec but it would be very convenient for our testing situation if I could make this work. Any suggestions?
Tags
<ruby><loops><testing><rspec>
Title
rspec: how can I continue test after first failure
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USPICyourBrain
UserOwnerUserId
1. USPICyourBrain
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POrspec: how can I continue test after first failure
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POrspec: how can I continue test after first failure
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.