Contributions
Re: Composite Project and the Resource Directory
Thanks for the script tip! I added a line testRunner.testCase.setPropertyValue( "ProjectDirectory", project.getPath()); and imported it with ${#[SuiteX#TestCaseX]#ProjectDirectory}/myDataFolder/myFile I would still like to see a custom property for this for composite projects, that could be used in the same manner as${projectDir} for non composite projects, so that project members don't have to run a script before importing files.5 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.5KViews0likes2CommentsRe: include assertion values in Assertion window
AABI sometimes use the rename (F2) option on simple assertions to display the asserted value, like "Match content of [node] = [expected result]", but this takes a lot of extra time to do. Would love to have the expected assertion values more easily displayed for the types of assertions where this makes sense.3.4KViews0likes0CommentsRe: Composite Project and the Resource Directory
I want to raise this same question again! The${projectDir} property gives me the path of the parent folder of my project folder, and not the project folder itself. For a non-composite project this makes sense as you could put resource files on the same level as your project xml file. For a composite project however, I want to use the relative project path, as it makes no sense to place my recource files outside the project folder. I have all my recource files in a folder called <Data>, so I want to my project resource root to be${projectDir}/[project_name] and refer to my file import paths as: <Data/filename.xml>. Now I have to set them to: <[project_name]/Data/filename.xml>, which also means that all project member must use the exact same name for their project folder. The last part is a problem with using Git, where you are allowed to rename your local project folder to anything. What makes it even worse is when importing a new project from Git in ReadyAPI, the user is asked to place the project in an empty project folder. If the name of this user created project folder does not match the Git repository name (project name), then all project members might end up with different paths to data recources, and import conflicts. I would like a property with path to my composite project root folder, without creating a custom property for this. The correct path is already in the value of the "Project property" calledFile, but I don't now how to refer to this property as it is not a custom property. Could this be done? I think the functionality of the "Recource root:${projectDir}" should be changed once the project is set to a composite project! Otherwise I see no obvious use for this functionality.5 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.6KViews0likes4Comments