Best Of

It sounds like you need to fill out some fields in the PDF, and then send the PDF somewhere. Filling out the fields will need to be done using a different application than SOAtest. You could then use the External Tool or Extension Tool in SOAtest to call that other application to make it part of your overall scenario.

Please use the echo.jsp provided with ParaBank. SOAtest includes a ParaBank example project which can be deployed locally. Alternatively, there is also the public deployment: http://parabank.parasoft.com/parabank/echo.jsp

The host ws1.parasoft.com is no longer publicly available. It has not been referenced in any documentation or tutorials since the SOAtest 9.8.0 release (Oct 24, 2014). The ParaBank demo application should be used instead.

@Ndey
you need to start with Testing from the Command Line Interface - soatestcli
There will be just one difference in commands to execute tests:

• in case that you want to execute one or selected TST in workspace, you have to include -resource option
• in case that you want to execute ALL TSTs in workspace, skip -resource option

Some examples of soatestcli call:

• command to execute all TSTs:
  soatestcli.exe -data "c:\APITest" -config "builtin://Demo Configuration"

• command to execute all TSTs but with non-default preferences:
  soatestcli.exe -data "c:\APITest" -config "builtin://Demo Configuration" -localsettingsmy_local.properties

• command to execute just one TST with non-default preferences:
  soatestcli.exe -data "c:\APITest" -config "builtin://Demo Configuration" -localsettings my_local.properties -resource "Login/Login.tst"
  In last case I have assumed that you have Login.tst in project folder called Login.
  In your case (as you want to run soatest using VBScript or batch file), call might looks like:
  VBScript template:

  Set oShell = CreateObject ("WScript.Shell")
  oShell.run "soatestcli.exe -data ""c:\APITest"" -config ""builtin://Demo Configuration"" "
  

batch file template:

    @echo off
    soatestcli.exe -data "c:\APITest" -config "builtin://Demo Configuration"

--
Ireneusz Szmigiel
http://www.catb.org/esr/faqs/smart-questions.html

Here is a groovy script we use to decode and encode

import com.parasoft.api.*
import java.lang.*
import javax.xml.bind.DatatypeConverter;

public String Decode(input, context) {

//Pull the encoded base64 string into the script.
a = context.getValue("Generated Data Source", "Variable_Name");
Application.showMessage("Variable_Name: " + a)


//Decode the string.
decoded = new String(DatatypeConverter.parseBase64Binary(a));
Application.showMessage("Decoded: " + decoded)
assert decoded.contains('SUCCESS')

//Encode the string. This should match the original string you pulled in to the script.
encoded = new String(DatatypeConverter.printBase64Binary(decoded.getBytes()));
Application.showMessage("Encoded: " + encoded)

return

}

I'd recommend using java.util.Base64 over DatatypeConverter. A couple reasons:

• The Base64 class is the "new" way of doing this, introduced in Java 8 whereas DatatypeConverter is what you had to use in Java 7 and earlier.
• DatatypeConverter is also part of the JAXB API which was removed from the core Java API since Java 11. Using "Base64" is safer if you want this code to also work with newer versions of Java.

Unfortunately there is no way to hide the value. The Traffic Viewer shows what goes across the wire so you see the value there even if it is masked in the environment variable.