search for: assert_

...of an API it turns into a long list of expect statements that the person reading the test can't easily grok and see how they're related. Here's an example from the formatv tests that I wrote: > > Replacements = formatv_object_base::parseFormatString("{0,-3}"); > ASSERT_EQ(1u, Replacements.size()); > EXPECT_EQ(ReplacementType::Format, Replacements[0].Type); > EXPECT_EQ(0u, Replacements[0].Index); > EXPECT_EQ(3u, Replacements[0].Align); > EXPECT_EQ(AlignStyle::Left, Replacements[0].Where); > EXPECT_EQ("", Replacements[0].Options);...

...05/11/17/building-a-plugin-on-rspec It seems that the benefit of BDD is that it makes it easier to use tests in the intial design. I guess I also like the languaging more. Do the more experienced developer think it''s a mistake for me to explore rSpec vs. just using the standard "assert_" type tests? thanks, Bryan -- Posted via http://www.ruby-forum.com/.

Hi, test "is_admin method is not visible" do get :is_admin assert_??? end is_admin is protected and should stay that way forever. What assertion do I use? M. -- Posted via http://www.ruby-forum.com/.

...nController::TestResponse.new end # Test party_link function passing staff def test_party_link_staff link_data = @controller.party_link(party(:twburges)) end end ---------------------------------------------------------------------- Note that we''re not even getting to an assert_* in test_party_link_staff(), because, well, we tried, and we just get an error, so we culled the assertions from the code I''m sending (so as not to confuse the issue). 1) Error: test_party_link_staff(HelperControllerTest): NoMethodError: undefined method `link_to'' for #<Help...

...and we need your feedback! As some of you may know, we have recently released the first public beta of a Ruby IDE called ''Steel'' for Visual Studio. Beta 0.5 has colour coding, code collapsing and various editing features (bracket matching, commenting, syntax error location etc.) plus a docked interactive console. At the end of this month we will release v 0.6 which has

...const char *name, enum test_predicate pred) { fprintf(stderr, "\n%s:%d test #%u \"%s\"%s%s\n", file, line, test_number, active_test_name, *subtest_info != '\0' ? " - " : "", subtest_info); fprintf(stderr, "ASSERT_%s_%s(%s%s%s) failed:\n", name, pred_name(pred), a1, a2 != NULL ? ", " : "", a2 != NULL ? a2 : ""); } void assert_bignum(const char *file, int line, const char *a1, const char *a2, const BIGNUM *aa1, const BIGNUM *aa2, enum test_predica...

As I work with Rails TestUnit tests I am reconsidering how to use cucumber features. It seems to me that it might be best to have a coherent view of how to arrange my test suites before I get much further into this. Now, so far I have considered three possibilities: 1. Use features exclusively. Create a feature file for each model, one for each controller and possibly an additional one for

CRAN (and crantastic) updates this week New packages ------------ * disclapmix (0.1) Maintainer: Mikkel Meyer Andersen Author(s): Mikkel Meyer Andersen and Poul Svante Eriksen License: GPL-2 http://crantastic.org/packages/disclapmix disclapmix makes inference in a mixture of Discrete Laplace distributions using the EM algorithm. * EstSimPDMP (1.1) Maintainer: Unknown Author(s):