search for: test_case

The vsock_diag.ko module already has a test suite but the core AF_VSOCK functionality has no tests. This patch series adds several test cases that exercise AF_VSOCK SOCK_STREAM socket semantics (send/recv, connect/accept, half-closed connections, simultaneous connections). The v1 of this series was originally sent by Stefan. v3: - Patch 6: * check the byte received in the recv_byte() * use

...ng the way and things ''were'' working out with my ''rake spec'' until I tried to follow some examples for test Authlogic with rspec. I ''think'' what started the problems was when I added at the top of a controller test: require ''authlogic/test_case'' After doing that, I seemed to have to re-run ''bundle install'' (or maybe that was triggered because I touched the Gemfile, even though I ended up not adding changes to it.) I was prompted with: git://github.com/odorcicd/authlogic.git (at rails3) is not checked out. Ple...

The vsock_diag.ko module already has a test suite but the core AF_VSOCK functionality has no tests. This patch series adds several test cases that exercise AF_VSOCK SOCK_STREAM socket semantics (send/recv, connect/accept, half-closed connections, simultaneous connections). Stefan: Do you think we should have a single application or is better to split it in single tests (e.g.

...====================== --- test/mocha/auto_verify_test.rb (revision 1114) +++ test/mocha/auto_verify_test.rb (working copy) @@ -155,6 +155,11 @@ assert_equal ''named_stub'', stub.__mock_name end + def test_stub_should_respond_to_already_defined_method + stub = test_case.stub(:id=>"id") + assert_equal "id", stub.id + end + def test_should_create_greedy_stub_with_name greedy_stub = test_case.stub_everything(''named_greedy_stub'') assert_equal ''named_greedy_stub'', greedy_stub.__mock_name

...tialize @test_array = [] puts "Called constructor" puts @test_array.size # This Works!!! end end Test/app/controllers/test_object_controller.rb ------------------------------------------------------------------ class TestObjectController < ApplicationController def test_case @test_object = TestObject.new puts @test_object.test_array.size # This doesn''t work!!! end end http://localhost:3000/test_object/test_case ------------------------------------------------------------------ undefined method `test_array'' for #<TestObject:0x39e4030...

I upgraded a working app from rails 2.1 to 2.3.2. Now when I run rake test:units I get this error: /usr/lib/ruby/gems/1.8/gems/ activesupport-2.3.2/lib/active_support/test_case.rb:17: superclass mismatch for class TestCase (TypeError) I generated a new test app and all tests run OK. For the upgrade I ran rake:update and renamed the class in test_helper to ActiveSupport::TestCase. Also renamed the classes in all unit tests and to inherit from ActiveSupport::TestCase and...

...c.edu/mailman/listinfo/llvmdev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150319/7128bb93/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: test_case.ll Type: application/octet-stream Size: 3976 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150319/7128bb93/attachment.obj>

...| | long unsigned int | %u test-mech.c:338:12: warning: passing argument 2 of ?test_mech_construct_apop_challenge? from incompatible pointer type [-Wincompatible-pointer-types] 338 | &test_case->len); | ^~~~~~~~~~~~~~~ | | | size_t * {aka unsigned int *} test-mech.c:195:77: note: expected ?long unsigned int *? but argument is of type ?size_t *? {aka ?unsigned int *?} 195 | test_mech_construct_apop_challenge(unsigned int connect_uid,...

...the test suite so we can tell what actually failed? You can download full log of e.g. i586 build from OBS here: https://build.opensuse.org/build/home:stroeder:branches:server:mail/openSUSE_Tumbleweed/i586/dovecot23/_log Excerpt of failed test: [ 576s] test-mech.c:370: Assert(#1) failed: strcmp(test_case->username,username) [ 576s] "testuser" != NULL [ 576s] test-mech.c:380: Assert(#1) failed: request->failed == FALSE [ 576s] auth mech APOP 2/84 .................................................. : FAILED Ciao, Michael.

...+ exit(EXIT_FAILURE); >+ } >+ >+ if (shutdown(fd, SHUT_RD)) { >+ perror("shutdown"); >+ exit(EXIT_FAILURE); >+ } >+ >+ control_writeln("SHUTRDDONE"); >+ control_expectln("CLIENTDONE"); >+ >+ close(fd); >+} >+ > static struct test_case test_cases[] = { > { > .name = "SOCK_STREAM connection reset", >@@ -1250,6 +1378,16 @@ static struct test_case test_cases[] = { > .run_client = test_seqpacket_msg_peek_client, > .run_server = test_seqpacket_msg_peek_server, > }, >+ { >+ .name = "SOCK_...

...d it is not failing. >+ exit(EXIT_FAILURE); >+ } Moving the pointer correctly, I would also check that there is HELLOWORLD in the buffer. Thanks for adding tests in this suite! Stefano >+ >+ control_writeln("REPLY1"); >+ >+ close(fd); >+} >+ > static struct test_case test_cases[] = { > { > .name = "SOCK_STREAM connection reset", >@@ -1038,6 +1114,11 @@ static struct test_case test_cases[] = { > .run_client = test_seqpacket_inv_buf_client, > .run_server = test_seqpacket_inv_buf_server, > }, >+ { >+ .name = "SOCK_ST...

...e D:\web\Sites\demo>ruby test/unit/tester_test.rb Loaded suite test/unit/tester_test Started .E.... Finished in 0.234 seconds. 1) Error: testers(ActionController::TestCase): ArgumentError: wrong number of arguments (0 for 1) D:/web/Sites/demo/vendor/rails/actionpack/lib/action_controller/ test_case.rb:48:in `initialize'' D:/web/Sites/demo/vendor/rails/actionpack/lib/action_controller/ test_case.rb:48:in `new'' D:/web/Sites/demo/vendor/rails/actionpack/lib/action_controller/ test_case.rb:48:in `setup_without_fixtures'' D:/web/Sites/demo/vendor/rails/activere...

...fore running the specific test........ We are running the test_suite in non restricted......... Inside file subunit.c and func :: suite_start Inside file subunit.c and func :: suite_start and suite_name :: write progress: 4 Inside file subunit.c and func subunit_test_name:: test_name :: write and test_case_name :: write Inside file subunit.c and func subunit_test_start:: test_name :: write and test_case_name :: write test: write time: 2011-11-10 18:37:03.361930 Inside test_write :: The base_dir is \testwrite\test.txt Inside RAW.WRITE (test_write)....and test_case name is :: write Inside RAW.WRITE...

Test case attached. It is not a test case that works within the llvm test-suite yet, but it does demonstrate the problem. I would like some advice on how to modify this test_case so that it can be added to the automated llvm test cases. On 15 September 2013 23:02, David Majnemer <david.majnemer at gmail.com> wrote: > The attached patch includes no test-case and isn't consistent with the > rest of the file: > - constants should be on the right hand sid...

The attached patch includes no test-case and isn't consistent with the rest of the file: - constants should be on the right hand side of comparisons - the braces around your single line 'if' aren't needed. On Sun, Sep 15, 2013 at 2:39 PM, James Courtier-Dutton < james.dutton at gmail.com> wrote: > I attach a patch that fixes this bug. Applies to llvm 3.4svn > >

Guys, I''ve created a plugin, i wanna put my automated test there. However, I got bad file descriptor error when i run the test like normal unit test file: "ruby plugins/acts_as_fox/test/acts_as_fox_test.rb" How to test a plugin? Also, is it right to say that I should only put my unit tests (but not functional test for example) for the plugin in the plugin test folder?

...gt; I'm trying to update openSUSE package on OBS [1] which builds for >>> various OS versions and hardware platforms. To me it seems that a test >>> fails on 32bit platforms: > > Excerpt of failed test: > > [ 576s] test-mech.c:370: Assert(#1) failed: > strcmp(test_case->username,username) > [ 576s] "testuser" != NULL > [ 576s] test-mech.c:380: Assert(#1) failed: request->failed == FALSE > [ 576s] auth mech APOP 2/84 > .................................................. : FAILED I'm getting the same issue on a CentOS 6 i3...

On 18/08/20 2:15 pm, Peter wrote: > I'm getting the same issue on a CentOS 6 i386 build: > > test-mech.c:371: Assert(#1) failed: strcmp(test_case->username,username) > ??????? "testuser" != NULL > test-mech.c:380: Assert(#1) failed: request->failed == FALSE > auth mech APOP 2/84 .................................................. : > FAILED > > Full log of tests is at https://paste.centos.org/view/33771454...

Below every page in the browser i get: "Loaded suite dispatch.cgi Started Finished in 0.000225 seconds. 0 tests, 0 assertions, 0 failures, 0 errors" I''m not sure if i changed something or someone else did it, but now i don''t know how to get rid of it. It has something to do with testing, right? How to switch it off? -- Posted via http://www.ruby-forum.com/.

Lucene''s standard analyzer splits words separater with underscores. Ferret doesn''t do this. For example, if I create an index with only document ''test_case'' and search for ''case'' it doesn''t find anything. Lucene on the other hand finds it. The same story goes for words separated by colons. Which analyzer should I use to emulate Lucene''s StandardAnalyzer behavior? Thanks. Kent -- Posted via http://www...