Forum Discussion

steven_yetter's avatar
steven_yetter
Contributor
3 years ago

"Common" or "Lib" Project

Test Project Library   If I have a parameterized test that is used by several other Test Projects in my TestComplete suite, should I put that test with others in its own TestComple Project that doe...
rraghvani's avatar
rraghvani
Champion Level 3
3 years ago

While developing, if you find yourself writing code that does the same thing, then it's ideal to make it as a function and reuse it. Also, don't make the functions complicated, break it down into sections if you can.

 

If the name of your application that you are testing is called "spkpro", then it's not necessary to name all if your function or projects, appending with "_spkpro".

 

My Project Suite is called "Asset Liability Suite", within this suite, I have many projects which tests different areas of the tool and are named appropriately (which doesn't include the project suite name). Before each tests are run, I import data into the DB; launch the browser; goto the URL; and login into the application. Tests are executed. Finally, perform a clean-up to get the DB back to it's original state.

The actions shown in Italics, are functions that are performed all the time before/after tests are executed. These are all stored in a Common project, which can then be used within the project suite.

 

See https://community.smartbear.com/t5/TestComplete-Questions/Calling-units-from-one-project-to-another-without-Importing-them/m-p/238186

  • steven_yetter's avatar
    steven_yetter
    Contributor
    3 years ago

    I saw that article about code from other projects?   What about using keyword tests from other projects?

     

    Project  Test-CSA

         Run IsoSpeak.  (and verify Splash Windows contents for user name etc.)

         Select Admin Mode

         Select Load Project parameter C-SA Path   (and verify Project Summary for C-SA)

         Select Project-Info (and verify experiments for C-SA )

         Select Data Processing (and verify experments data processing status for C-SA)

         Select Export and verify Message box of export type buttons

          Select Score Export (and verify file browser)

          Enter path to export to for C-SA

     

    Project  Test-I-IM

         Run IsoSpeak.  (and verify Splash Windows contents for user name etc.)

         Select Admin Mode

         Select Load Project parameter I-IM Path   (and verify Project Summary for I-IM

         Select Project-Info (and verify experiments for I-IM)

         Select Data Processing (and verify experments data processing status for I-IM)

         Select Export and verify Message box of export type buttons

          Select Score Export (and verify file browser)

          Enter path to export to for I-IM

     

    Select Admin Mode is a step common to both projects.  A test project is for a chip type like C-SA and C- is a chip family.  We have approximately 5 chip families.  There is no way to have Select Admin Mode keyword test in a library project, without converting the keyword test to script?