Forum Discussion

vpachpute1's avatar
vpachpute1
Frequent Contributor
8 years ago

ReadyAPI 2.0: To apply assertions inside log files

Hi   I have one scenario that, 1 Purchase using API. And validate response - Working fine. 2. Inside my application, there is one log file as trans.log     - After the purchase, there are follow...
  • groovyguy's avatar
    groovyguy
    8 years ago

    If you are able to clear the trans.log file and have access to it, you can use the following groovy script:

     

    PrintWriter writer = new PrintWriter("/path/to/log/trans.log");
writer.print("");
writer.close();

    That will zero out the file and erase ALL contents of it. From there, you need a groovy script to parse the contents of the log.

    def fileContents = new File("/path/to/log/trans.log").text.split("\n");


for (line in fileContents)
{
	if (line.contains("<v:name>purchase-all</v:name>"))
	{
		log.info(line);
	}
}

    That's a basic proof of concept that you should be able to modify to do what you want.

vpachpute1's avatar
vpachpute1
Frequent Contributor

Hi nmrao

 

You are exactly right. Log files are generally large in size. In my other scenarios, I am doing same thing. Most of the assertions are at the API level and DB level.

 

But in some scenarios, when I sends API request, internally application triggers some requests to other application and needs to validate these things. e.g.

1 When I purchase using API, I got success message in API response. But internally it triggers notifications call and notification is sent to customer as "Thanks for purchasing this ..... etc". So these things needs to validate in logs weather notification is sent or not.

2. And these notifications are not stored in any DB. So not able to apply assertions in DB.

 

So I needed to validate in log files.

 

Regards

Vishal Pachpute

nmrao's avatar
nmrao
Champion Level 3
8 years ago
May be you should raise an enhancement in the application you are working with saying the issue and need a proper way to test it instead of just relying on log.

Some times even the message is just logged could also be wrong (in the sense, it is just logged, but did something different).
  • groovyguy's avatar
    groovyguy
    Community Hero
    8 years ago

    I agree with nmrao, and I apologize that I didn't realize the implication of dealing with a log file that's likely huge in size. Is the message you are looking for going to have ANY unique identifiers present in the log? Otherwise, if you are going by timestamp alone, that is a lot harder. 

     

    You state that you have to verify that <v:name>purchase-all</v:name> has to exist in the log file, but it has to exist after you send the request, ignoring any previous occurrences. Is there anything in the log to accompany "<v:name>purchase-all</v:name> " that would uniquely identify it as YOUR request? Otherwise going by timestamp alone may lead to false positives. 

    • vpachpute1's avatar
      vpachpute1
      Frequent Contributor
      8 years ago

      Hi

       

      Yes, actually these values are not unique. This might be because of other previous requests. but we can resolve this using following strategy.

       

      Using groovy

      1. How can we clean the contents of trans.log file.

      Note: If we clean the contents of trans.log file before sending requests, whatever large data is there will be erased and issue of previous large data will be solved.

      2. Then send data purchase API

      3. Then <v:name>purchase-all</v:name> will be unique. How can we verify verify using groovy weather this <v:name>purchase-all</v:name> present or not.

       

      I might be wrong somewhere. Please correct me.

       

      Regards

      Vishal

       

      • groovyguy's avatar
        groovyguy
        Community Hero
        8 years ago

        If you are able to clear the trans.log file and have access to it, you can use the following groovy script:

         

        PrintWriter writer = new PrintWriter("/path/to/log/trans.log");
writer.print("");
writer.close();

        That will zero out the file and erase ALL contents of it. From there, you need a groovy script to parse the contents of the log.

        def fileContents = new File("/path/to/log/trans.log").text.split("\n");


for (line in fileContents)
{
	if (line.contains("<v:name>purchase-all</v:name>"))
	{
		log.info(line);
	}
}

        That's a basic proof of concept that you should be able to modify to do what you want.