path
Discussion List
-
incremental scan on docker container
Hi We are running cpptestcli to scan our code inside a docker container. Since we start with clean workspace every time, the scan takes too much time. To try to resolve it, we copied ".cpptest" folder to a shared location, then, on the next run, downloaded it to the workspace. the problem is that we still see long scans…
-
Pass virtual assets ID? into the URL path
So I have this JSON responder... The Input Mode is Multuple Responses and each of these has been giving a name matching what should be set in the URL so for instance; List of Multiple Responses; foo1 foo2 foo3 url example; server01..parasoft.local/data/layer/foo1/map So in my application if url directs to ;…
-
Workspace and project path from script
I need to access files saved to my workspace from Groovy script. How can I get the path to my workspace and project?
-
Links to test file locations
Following the paragraph "Executing Existing CppUnit Test Cases" from the C++_userguide I added test files into tests subdirectory of my project. The "Test suite file search patterns" is set to "${project_loc}/tests/*". The problem is that files in the tests directory which are linked to somewhere else are not executed.…
-
Local pathnames in the .parasoft file.
Sharing projects and test assets through source control requires checking in a .parasoft file (if present) among others, but sometimes it contains local pathnames. For a number of technical reasons, when updating that .parasoft file, C++test will dump all (internally registered) properties (with their default values, which…
Popular Tags
- SOAtest 454
- legacy 440
- Virtualize 207
- C/C++test 179
- scripting 106
- .parasoft 82
- unit testing 64
- Parasoft Virtualize 61
- Announcement 61
- static analysis 58
- jtest 57
- dotTEST 48
- assertions 47
- C++ test 43
- API Testing 39
- cli 38
- automation 37
- data source 37
- xpath 35
- java 33
- reporting 33
- LoadTest 32
- SOAtest Virtualize 32
- ctp 30
- JSON 29