Forum Discussion

UhsBat's avatar
UhsBat
Occasional Contributor
4 years ago

DataSource Step is failing in Jenkins with ReadyAPI 3.5.1 docker image

I am running my ReadyAPI projects in Jenkins using the Latest ReadyAPI docker image. Now facing issue in whatever new projects created with version 3.5.1. I have a DataSource step and reading data f...
  • sonya_m's avatar
    sonya_m
    4 years ago

    Thank you for investigating PrathapR !

     

    UhsBat I checked with the team, we didn't find a known bug immediately, contacting support would be the best next step since this needs deeper investigation. 

    If you post the final solution here, this will be really helpful for the community! Thank you!

PrathapR's avatar
PrathapR
Frequent Contributor

Hey UhsBat 

 

Are you using relative path(EX:${projectDir}/InputData/EmployeeData.xlsx) or Dynamic Paths(Ex: EX: C://InputData/EmployeeData.xlsx) in your data source?

 

Thanks!

UhsBat's avatar
UhsBat
Occasional Contributor
4 years ago

Hi PrathapR

 

Thanks for the reply.

 

I am setting Excel path dynamically using below code.

def objProject = context.getTestSuite().getProject();
def projPath = objProject.getPath()
testSuite.setPropertyValue("DataSourcePath", "${projPath}${File.separator}data${File.separator}CustomerIdScenarios.xlsx")

And in DataSource I am passing the "${#TestSuite#DataSourcePath}".

 

It was working fine till ReadyAPI  V3.5 in both local ReadyAPI and Jenkins.

 

Now the latest ReadyAPI giving error in Jenkins alone.

I am using the latest ReadyAPI docker image to run suites.

  • PrathapR's avatar
    PrathapR
    Frequent Contributor
    4 years ago

    If it was working in 3.5 and not now, may be there is some issue with current version.

     

    Hey sonya_m  do you have any info on this issue?

     

    Thanks!

    • sonya_m's avatar
      sonya_m
      SmartBear Alumni (Retired)
      4 years ago

      Thank you for investigating PrathapR !

       

      UhsBat I checked with the team, we didn't find a known bug immediately, contacting support would be the best next step since this needs deeper investigation. 

      If you post the final solution here, this will be really helpful for the community! Thank you!

      • UhsBat's avatar
        UhsBat
        Occasional Contributor
        4 years ago

        Sorry for the late response.

         

        Seems like they have fixed it as part of (RIA‑15414) in 3.5.2 version.

         

        Its working fine after pulling ReadyAPI docker image 3.5.2