Best method for executing tests

2 posts, 0 answers
  1. Melinda
    Melinda avatar
    4 posts
    Member since:
    Aug 2011

    Posted 09 Oct 2012 Link to this post

    I'm attempting to run some testcases that I created in Test Studio by simply using ArtOfTest.Runner.exe.

    I have two tstest files in a root folder, a test list file in a folder called "TestLists", and the DLL for the project in the "bin" folder.
    With that setup I can then run the test using this command:
    ArtOfTest.Runner.exe list="C:\temp\TelerikTest\TestLists\MelindaList.aiilist"

    However, if the DLL is not in a folder called "bin", or if the tstest files (the ones in the test list) are not one folder up from the test list, everything fails to run. I can't find anyway to specify the location of the DLL file or change where the test list is looking for the testcases.

    Can anyone help with the proper way to deploy and execute a test list using ArtOfTest? Not every machine that I want to run the tests from will have Visual Studio with the Telerik ad-on, so I want to be able to run the tests independently from Visual Studio or Test Studio, but I'm having a hard time figuring out the best practices for deploying the tests once I've written them. Any advice would be appreciated.
  2. Mario
    Mario avatar
    8 posts

    Posted 12 Oct 2012 Link to this post

    Hello Melinda,

    Thank you for your question.

    Let me start by point you to a useful page in our online documentation regarding the ArtOfTest Runner. Specifically the section to note would be how to bring up the options menu using the following command 'ArtOfTest.Runner.exe /?'. The only relevant property you could change from here would be the path to the project root folder directory, however the correct folder structure within this path for Tests and TestLists would still need to be intact as you described. The .dll files along with the Bin folder are necessary because the .tstest file specifically relies on this structure. Buried within the .tstest file is a pointer to this bin folder and the name of the dll to load at run time. If the folder is not there, or the name of the dll does not match what the .tstest is expecting then you will get the error you are seeing.

    I find when transferring a Project, simply creating a copy of the entire project folder (normally or through a zip file) and moving it to the Run-Time machine is the easiest way to escape all of these issues.

    Let me know whether you have any further questions.

    the Telerik team
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
Back to Top