ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

SV File in .mari and .mar not always included, even though we 'force' inclusion

book

Article ID: 145637

calendar_today

Updated On:

Products

CLOUDTEST CA Application Test CA Cloud Test Mobile MOBILECLOUD Service Virtualization

Issue/Introduction

We have a .js file that we use to create logging for our test cases. DevTest is inconsistent in how it 'includes' this .js file in .mar files. We open the .mari and ensure that it IS part of the .mar. Then we deploy the .mar to the Portal as a project. Then we try to kick of the test or the suite from the Portal. Sometimes the .js file is picked up and runs correctly. Other times it is NOT picked up and the logging function does not work. The problem is that sometimes it works and sometimes it doesn't work.....for the same project!  Currently, the only work around is to add the .js file to EVERY test case as a dataset in order to 'trick' DevTest into recognizing that the .js file is a dependency needed to run the test. This was never an issue in DevTest 9.1.
 
 

Environment

Release : 10.5

Component : CA Application Test

Resolution

Solution Steps:

1: Define a property for .js file path(i.e. applicable to any external file which is required in the project as a dependency) in the project.

MYJSFILE={{LISA_RELATIVE_PROJ_ROOT}}/Data/myJSfile.js

 

2: Use this property in the places where this file is required.

 

load("{{MYJSFILE}}");

 

This dependency will always be included in the .mari file and the external file will be added in .mar.

 

Please find the below snapshot of the downloaded .mar file content for your reference.

Attachments