Forum Discussion

Novari-QA's avatar
Novari-QA
Frequent Contributor
8 years ago

Keyword tests are unable to identify functions

Keyword tests are unable to to see function.names.  See the code below. The script is called LoginPage.js var page = { form: { username: Aliases.browser.pageLogin.form.textboxUsername, ...
  • tristaanogre's avatar
    tristaanogre
    8 years ago

    Exactly... also, prevents the "copy paste" code problem from your original OP...  it's really generally bad practice to have the same code showing up almost EXACTLY the same way in multiple places... better to have the code modularized in one spot that is "smart" enough code to do what it needs to no matter where it is called.  Again, keep in mind, you're creating building blocks for your testers...  if you give them too many blocks that look almost exactly the same, you'll end up with more mistakes as the testers can get easily confused... 

Novari-QA's avatar
Novari-QA
Frequent Contributor

certainly my example can be simplified as stated above, however the pages get more complex. I am trying to build a bunch of predefined objects which a "non" coder can utilitize in keyword tests. 

I could just make a ton of scripts rather a ton of function. So instead of stating LoginPage.js, I can have a folder called LoginPage with a script called Login.

Hmm. 

tristaanogre's avatar
tristaanogre
Esteemed Contributor
8 years ago

However works for you works... but the limitation is that "Run Script Routine" does just that... runs a script routine... it doesn't run a method of an object unless that object is exposed in some way... Scripts != objects... they are files... units of code... they may CONTAIN objects but they are not seen as objects by TestComplete.

  • Novari-QA's avatar
    Novari-QA
    Frequent Contributor
    8 years ago

    Is it possible to share a brief overview on how you would organize your scripts / keyword tests?  Perhaps I am trying to go about things in a bad way.

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      8 years ago

      What you have going on is not wrong... you have a unit of code specifically to handle stuff on the LoginPage.  That's fine.  It's simply a matter of, instead of trying to create an object called "Login", let the file be that... and then create methods, functions, etc., within that code unit that will execute tests within your KeywordTests.  What I posted before is a simplified example of that.  You have a function that performs the login task on the login page and, when you call it, you determine if you're going to check for a positive outcome or a negative outcome.  Each page you want to test, you could easily organize the same way... have a unit of code that contains functions to perform tests/actions on that page.

       

      Then, when your testers need to construct test scenarios, they just drag in the methods from the appropriate unit and set the parameters. Having it organized by page is a good trigger to your testers that "I want to do something on the login page, I go to the Login unit and grab the function I want".

       

      I THINK cunderw does something similar, if not exactly the same, and it works well for him.

      • Novari-QA's avatar
        Novari-QA
        Frequent Contributor
        8 years ago

        However there is a major issue with that solution: 

        Within my application I have objects duplicated in multiple locations throughout.  Since I cannot name a class the same thing twice I am forced to predefine the class or postdefine the class with a unique name.

        For example, in multiple locations on our website we have a feature called PrivacyModal. It is the same modal, but acts differently depending on its state and location in the application. 

        Currently since I cannot build my scripts this way, I have to organize the scripts a different way. My new method has me creating a folder called [page] with sub classes which are the actions on the page. 

        In the example of logging into the system.

        What I want:
        LoginPage.js

        With an object called PrivacyModal
        - and this object has functions; PrivacyModal.Close, PrivacyModal.Open, PrivacyModal.Toggle
        However since we cannot do this I have to bring everything up one level

        What I have now:
        Folder called LoginPage

        Class called PrivacyModal.js
        Functions called; Close, Open, Toggle.

        This works, until i get to another page that has that funcationality. lets just call it splashpage.js

        since PrivacyModal.js already exsists, we cannot call it that. So i am forced to give it a unique name



        I hope this makes my issue clear.