search for: test_something

...is Op 6 feb. 2018 om 20:27 heeft Micha Ballmann via samba <samba at lists.samba.org> het volgende geschreven: Thanks for help, this is a new domain controller without any modifcations, except one GPO. I have the "Default Domain Policy" and created an addtional GPO, named "test_something". Both are linked at the top of the domain. I configured at the "test_something" GPO: # Interactive logon: Do not require CTRL + ALT + DEL -> activate # Interactive login: Do not displa last user name -> activate Security Filter, by default:  * Authenticated Users Delegat...

Thanks for help, this is a new domain controller without any modifcations, except one GPO. I have the "Default Domain Policy" and created an addtional GPO, named "test_something". Both are linked at the top of the domain. I configured at the "test_something" GPO: # Interactive logon: Do not require CTRL + ALT + DEL -> activate # Interactive login: Do not displa last user name -> activate Security Filter, by default: * Authenticated Users Delega...

On 2/6/2018 1:42 PM, Robert Marcano via samba wrote: > On 02/06/2018 01:44 PM, Micha Ballmann via samba wrote: >> Hello, >> >> i have a testing environment, 2 DCs Ubuntu 18.04, SAMBA 4.7.4 - MIT >> Kerberos (clean, not upgraded). I just wan to create/activating a >> simple GPOs. >> >> # Interactive logon: Do not require CTRL + ALT + DEL -> activate

...st, and a mock expectation was to blame, the test''s failure / error messages don''t give enough info. I''ve had to resort to def teardown mocha_verify end which just gets tedious. I''ve created a patch against trunk v164 and included it below. Example: def test_something mock = mock("some mock") mock.expects(:message) flunk # or fail end I''m expecting to get both the flunk / fail message AND the Mocha expectation failure. It''s a very minor change, but I''m interested in what you guys think, -Zach

Hi, I something like: def test_something @object = Object.create(...) @object.update_attribute(...) assert_equal "changed", @object.attribute end The problem is that in the assertion, @object still holds the old values. Isn''t there a reload! method to reload the @object values? -- Posted via http://www.ruby-foru...

I''ve got unit tests for a class library that I''m using in a rails project. Currently this is the only project using this library so I would like to keep the classes and tests in the rails project. I moved the classes under [app]/lib. I currently have the tests in [app]/test. It would be great if these tests were run every time I run ''rake''. What is everyone

...is going to be removed. I like the concept of clean, readable tests, however I also like to test as efficiently as possible. For some tests, I''ll take the approach of putting test assertions inside the parameter block, and always returning true. This is a contrived example: def test_something mock = mock("some_mock") mock.expects(:foo).with do | param_that_is_a_string, param_that_is_a_model | assert_match(/something-for1/, param_that_is_a_string) assert param_that_is_a_model.valid? true end.returns("blah") end Again, I''m not agains...

paul.allton at uk.bnpparibas.com wrote: > I''m a big fan of automated UI testing (i.e. driving the UI from some robot API). I appreciate this > is potentially a whole new project, but does wxwidgets provide a method of clicking buttons, > typing into components ... if so, would it be technically possible to expose this in wxruby. I like automated UI testing too, but

While running tests, we would like to instrument some of the classes under test. We still want the classes to do exactly what they currently do, but we would like them to do more when running in the test environment. Clearly we can (and currently do) just extend the objects "on the fly" where necessary, but this is a bit messy - we''d like some centralised way to always