Michael Thomas admin

About

Username
Michael Thomas
Joined
Visits
119
Last Active
Roles
Admin, Staff
Points
12
Posts
8
Badges
2
  • Creating a Default Dashboard for New DTP Users

    Requires: DTP Enterprise Pack.

    Within DTP, a default dashboard is created for users who logs in for the first time.

    You are able to modify the default dashboard by modifying the default.json file under the guidance in: https://docs.parasoft.com/display/DTP532/Defining+New+Dashboard+Templates

    The attached DTP Template Creator is a DTP Workflow that will allow users to modify the default dashboard without knowing the inner workings of the default.json file.
    1. Download, Install, and Deploy the DTP Workflow.
    2. Create the dashboard from scratch. (Note: Do not create a dashboard from template.)
    3. Add your dashboard ID to the Set DashboardId node as described by the comment node and DTP Template Creator documentation.
    4. Click the button located on the Start DTP Template Creator node.

    6. Go to DTP_HOME/grs/dashboard/builtin and put default.json in a backup folder.
    7. Grab the contents of the output from the template as described in the DTP Template Creator documentation and add them to a new default.json file within DTP_HOME/grs/dashboard/builtin.

    From now on, a user will get use the modified dashboard if they log into DTP for the first time.

  • Re: SOATEST - How to assert on blank values

    Hi Testuser,

    Does an empty element represent a null value or no element in the response? If no element in the response in the response represents a null value, you want to use Occurrence Assertion. If no value in the element represents a null value, you want to use Has Content Assertion. Please let me know if this helps.

  • Re: Testing REST (GET) service that needs Excel and Database data sources

    Hi Diego,

    There are a couple of consequential reasons as to why you may be experiencing no data. Currently, I only have an assumption of your use-case. Please verify.

    1. It seems as if you have a setup test which reads from the Excel Datasource and input data to your database.
    2. You run a SQL query to get a particular id from that database.
    3. You run a GET REST request using that id.
    4. You run a tear down test which removes all of the information from the database based on the Excel Datasource.

    From the statement, "I know this can be easily done by using a database data source..." I am assuming that you were successful at using the Database Datasource. If not, please verify that this works using the database Datasource.
    Rather than using the Database Datasource, why not try using the DB Tool instead of the Database Datasource as shown by the image below. After your setup test, the DB Tool can query for the data, and store it into an XML Data Bank. Your messaging client can grab the results from your XML Data Bank. The image below represents the setup I would use for the use-case above. Please let me know if this helps.