Service Virtualization

 View Only
  • 1.  DEVTEST Portal: Monitor-->CVS Overview to display the last run status

    Posted Jul 09, 2020 07:29 PM
    Hi Team,

    Need a help related to the visualization CVS overview page.
    Monitor--> CVS
    The Overview tab under CVS display the monitor status as Unknown (As the monitor created runs once in 12hrs) so wanted to know if there any ways we can keep the last run status there for each monitor. Currently after 3hrs of the monitor run the status will be changed to Unknown.

    Thanks,
    Sagar Adyanthaya


  • 2.  RE: DEVTEST Portal: Monitor-->CVS Overview to display the last run status

    Posted Jul 10, 2020 12:21 AM
    Hi Sagar,

    Sometimes, the status unknown means  that the service is deployed and due to run for the first time and sometimes it could be because of something expected with the associated test case/suite as part of execution. 

    Assume you have 2 monitors [Test2 is ye to be executed]

    Once executed, its status will be updated accordingly.

    For detailed history of execution, you can use Reporting --> Testing --> Test/Suite Execution history Report  this could be exported as well.

    Thanks

    ------------------------------
    Regards,
    Vaibhav Jain
    Capgemini
    ------------------------------



  • 3.  RE: DEVTEST Portal: Monitor-->CVS Overview to display the last run status

    Posted Jul 10, 2020 08:22 AM
    Hi Vaibhav,

    Thanks a lot for the inputs.
    I see the previous status as completed. 
    The Monitor created runs every 12hrs suppose if it runs  at 6 AM till 9-10AM i will be able to see the status as Green (Completed) but after 10AM it shows Unknown(light Grey) and at 6PM again it shows Green(Completed), so wanted to know is there any setting which can be changed so that the monitor shows the last run Status.

    Thanks,
    Sagar



  • 4.  RE: DEVTEST Portal: Monitor-->CVS Overview to display the last run status
    Best Answer

    Posted Jul 10, 2020 11:43 AM
    Hi Sarag,

    Are there any errors or warnings in the execution report for the test suite.   Try running the test case with a small set of test data and try to observe if the issue persists. It is not easy to diagnose the actual issue without looking into the test case/suite.

    Also, check for java heap size or maxout utilization.

    Thanks


    ------------------------------
    Regards,
    Vaibhav Jain
    Capgemini
    ------------------------------