Good news that you are getting back to Tellurium. I prefer to create a directory "user-extensions" or just "extension" in the src/main/resources directory and once the code is compiled, the extension directory should be under the classes directory so that you should be able to reference it from the extension directory directly. Lib is really a bad place to put it. What do you think?
Yes, I will add the user-extensions.js to Tellurium configuration file. For custom methods, we can simply delegate them to a custom class and pass onto the delegator class as we discussed before. On Mar 19, 10:34 am, Mikhail Koryak <[email protected]> wrote: > John, > The first step, which i really do need your help with in all this is > getting the custom user extensions support working in tellurium. We > need to modify the tellurium config file to allow for both: using a > predefined user-extensions.js or overriding it with your own. we will > need a tellurium user extensions js file where i will dump all my > jquery selector logic. > I think we need consensus on where the tellurium-user-extensions.js > will live. > > At my job, i am nearing that time when i need to write a bunch of > functional tests again, and it would be a good time to start doing > more work on the jquery selector. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "tellurium-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/tellurium-users?hl=en -~----------~----~----~----~------~----~------~--~---
