Best Of

Hmmm - since you are typing this into the browser and the browser doesn't understand the relative path, you have to type an absolute path. You could put the value into an environment variable, and use a different environment depending on what machine you are running on. Another option is to switch the input from "Fixed" to "Scripted" and write a simple script that uses the SOAtest API ScriptingContext.getAbsolutePathFile() that takes a relative path as argument and will resolve it relative to the directory in which the .tst file lives. See the Parasoft SOAtest Extensibility API JavaDocs for details on that API.

From that dialog you do not have the ability to select "text", since there are no text nodes that are a direct child of that div element. So in the dialog choose a different property (even though you don't want it), and finish the dialog. Then, in the Browser Validation Tool "Validations" tab, go to the validation that was just added, and type "text" in the "Element Property" field and update the Expected Value field to the value that you expect. This will cause it to get all text nodes that are direct or indirect children of the div node, and will allow you to do the assertion that you want to do.

Problem:
You are data driving an API with your SOAtest test and you have data validation requirements on an array of data the API returns. This can be problematic because depending on the request parameters, which you've externalized into a data source, you will receive varying length arrays coming back in the API response. Since traditional data sources are two-dimensional (columns and rows), there is a problem because you have to account for a third dimension. Instead of hitting your head against the wall wondering how to construct multiple data source sheets to manage this hierarchy, there is a nice application of XPath that makes this problem easier to overcome.

Solution:
Let's first take a look at how your data source can be constructed. This will also help to visualize the desired data validation described in the problem.

Here you can see I'm using a delimiting character '|' to separate the variable length accountIds I am expecting to see in my response depending on which data source row is being executed. Next, let's look at how the JSON Assertor in my SOAtest Test needs to be configured.

You can see the expected value is set to the Excel column that contains the delimiter we used. The magic that makes this validation possible is a customized XPath using the XPath function "string-join()".

Notice the string-join() function has two parameters. An XPath, and our delimiter String. You will want to start off with an XPath that locates all the accountIds in the response payload, and then use the string-join() function that will append your delimiting character in-between each node the XPath selects. If you want to learn more about the string-join() XPath function, see: https://www.w3schools.com/xml/xsl_functions.asp

And that's all it takes!

If I understand your scenario correctly, "Test Suite: Do Login" runs if "Test Suite: Account user is logged in" fails. In order to accomplish the same thing without the scenario failing, I would make the following changes:
1. Update "Test 1: Assert Logout button is visible" to store a value to a test variable, and make it so the test always succeeds regardless of whether logged in or not.
2. Update the test suite logic so that "Test Suite: Do Login" runs based on the value in the test variable, instead of based on test failure.

A hidden element could be hidden in one of two ways:
1. The element is not present in the DOM
2. The element is present in the DOM but has a property (or its parent has a property) that causes it to be hidden

For the first case, you probably would need to add an XML Databank to the Browser Contents to validate that the element is not there. For the 2nd case, you need to know which property causes the element to be hidden, and configure the Browser Validation Tool to check the value of that property.

Try this instead:

import com.parasoft.api.*;
import java.io.*;

public String verifyReport()
{
    File file = new File("C:/SoATest/Downloads/reportTab.pdf");
    Application.showMessage("The file " + file.getAbsolutePath() + " has " + file.length() + " bytes");
    file.delete();
    return "true";
}