Passing the module name into the method definition

ruby-talk
1

I've been building a harness for running watir tests it looks lke this
currently-

module CVLibrary
    def CVLibrary.cv_login(testinstance, testaddress, testuser,
testpass, testldap)
      # opens ie, goes to Central Vision and logs in with the
    # specified address, username, password and domain
     testinstance.goto(testaddress)
     testinstance.frame("main").text_field(:name,
"username").set(testuser)
     testinstance.frame("main").text_field(:name,
"password").set(testpass)
     testinstance.frame("main").select_list(:name,
"ldapDir").select(testldap)
     testinstance.frame("main").button(:name, "Login").click
  end

The test script includes the following
require 'watir'
require 'test/unit/assertions'
require 'CVlibrary'

include Test::Unit::Assertions

ie = Watir::IE.start()

CVLibrary.cv_login(ie,‘http://address.html’,‘name’,‘pass’,‘domain’)

What I don't understand is why, in the module, I'm explicitly having to
pass in it's own name? e.g. CVLibrary.cv_login

None of the examples

···

--
Posted via http://www.ruby-forum.com/.

2

Max Russell wrote:

I've been building a harness for running watir tests it looks lke this
currently-

module CVLibrary
    def CVLibrary.cv_login(testinstance, testaddress, testuser,
testpass, testldap)

....

What I don't understand is why, in the module, I'm explicitly having to
pass in it's own name? e.g. CVLibrary.cv_login

You're defining a class method (e.g. static in other regions of the programming world).
You actually don't have to pass the module name, and in the interests of refactoring it is also not advised.

You are better off doing:

def self.cv_login(...)

If you define
module CVLibrary
   def cv_login
   end
end

then you have an instance method, so you need to include the module in a class and then call the method from an instance of that class.
Cheers,
V.-

···

--
http://www.braveworld.net/riva

3

I don't believe I am defining a class at all... I had a look at the
Pragmattic Guide and it seems to do it the same way as I have, and I've
got my head round the instantiation bit now.

···

--
Posted via http://www.ruby-forum.com/.