search for: expected_result

...nction "demo_fn". Both functions are pasted below. I have a for loop within my function and it appears to only create new column for the last value in the argument "blup_datacut" which makes me think that I am not storing the values coming out of for_loop correctly. I have "expected_results", dataset, & functions pasted below to reproduce my problem and expected results. Any help will be greatly appreciate. # dataset dem<- structure(list(id = c("L1", "L2", "L3", "M1", "M2", "M3"), TEST_SET_NAME = c("A&quot...

...;. Both > functions are pasted below. > I have a for loop within my function and it appears to only create new > column for the last value in the argument "blup_datacut" which makes me > think that I am not storing the values coming out of for_loop correctly. I > have "expected_results", dataset, & functions pasted below to reproduce my > problem and expected results. > Any help will be greatly appreciate. > > > # dataset > dem<- structure(list(id = c("L1", "L2", "L3", "M1", "M2", "M3"), &g...

Hi all, The following only affects people who have bravely begun to experiment with the 2 day-old plain text story runner and definable groups of steps. For those who fit that bill, I just committed a few changes that will require you to make changes to your code. The StepMatchers class is now the StepGroup class. The step_matchers methods on PlainTextStoryRunner and StepGroup is now just

I''m still reading other people''s code and going over the books. As I was doing this a question sprang up in my mind. Is it wise for total newbies to attempt test driven development from the start? Basically, if you''re a newbie like me, chances are your tests might even be broken themselves. Or will attempting to write tests be good practice for actual coding as