I am using Loadrunner 2020 community edition. I have created a script in TruClient and when trying to replay in develop script mode, getting 'replay failed to start see vugen log for more details' error.
'logfile.log' was empty and 'mdrv.log' file had last replay log details when checked. Are those the files vugen referring to? What is the solution for this?
I faced the same issue, but was able to fix it as follows.
When I compiled the script, I did not see any errors in the output, so I checked the "Output -> Chromium(IE) - Interactive Replay" log which had several errors related to parameter files. When I fixed those, I was able to replay the script.
Output Log Path
Related
I get the below error when I run my xaction file in PUC (Pentaho User Console)
The Pentaho BI Platform reported an error while running an action sequence
Possible Causes:
ActionValidationException: RuntimeContext.ERROR_0035 - Action validation failed.
Action Sequence:farzan.xaction
Execution Stack:
EXECUTING ACTION: looking for the current user (KettleComponent)
Loop Index:N/A
I have attached xaction, ktr and database at:
https://drive.google.com/folderview?id=0BxjJ_gZ-RT2EemMtLTlYR1R3TUk&usp=sharing
It seems that your xaction file is throwing errors. Best way to find out your errors is to go search the log files. The path would be inside the BA Server: /pentaho/server/biserver-ee/pentaho-solutions/logs/.. There you will find log file. Check the error that is written in the logs.
[Also to note, from version 5 onwards, xaction support has been removed from the Pentaho releases.]
Hope this helps:)
I’m trying to integrate Bugzilla Testopia with Jenkins with the aid of the Testopia Plugin for Jenkins.
The general configuration is probably fine as the connection between Testopia and Jenkins is well established (Jenkins log says: ‘Connecting to Testopia to retrieve automated test cases’ and no error occurs then). However I’m unable to retrieve any information concerning Test Runs/Test Cases etc. from Testopia.
Moreover I cannot perform any of ‘Iterative Test Build Steps’. If I want to ‘Execute Shell’ in ‘Iterative Test Build Steps’ with Testopia Plugin no operation is carried out (even if I try: echo 12345 etc.). If I use ‘Single Test Build Steps‘ then shell command is executed.
My goal is to retrieve test class name from Testopia (it is stored in Testopia Test Case’s field - Automation/Scripts ) and then run maven build from Jenkins with this class name set as the parameter. Afterwards depending on the Jenkins build success or failure status I’d like to update the Test Case Status in Testopia.
How to fetch any information from Testopia into Jenkins?
Why any of ‘Iterative Test Build Steps’ is not executed?
Any clues? - Testopia Plugin site example wasn't too helpful for me.
Both Bugzilla and Jenkins are hosted on the same Ubuntu 14.04. I've got the latest stable versions of Jenkins, Bugzilla and Testopia.
Thanks in advance,
M.
EDIT:
Well this debugging does not work for me. I added a new log recorder with the 'ALL' level chosen and I cannot see any additional log neither in job's console output nor in the newly created logger output.
Maybe sth is wrong with my Testopia installation? Some more details concerning my configuration:
I've got Testopia installed on the same machine (as Jenkins) and usually I access it through: http://'ip_address'/bugzilla
- in Testopia plugin configuration my URL to Testopia installation is: http://'ip_address'/bugzilla/xmlrpc.cgi
- I've got only one bugzilla account - these admin's credentials I use in Jenkins
- sometimes in Jenkins I can see a warning concerning improper reverse proxy configuraiton - maybe it has sth to do with the problem
After job execution all Testopia's fields are 0 - Run Id, Build Id etc. - which obviously indicates that no information was successfully retrieved from Testopia.
Any ideas how to check why I cannot retrieve any information from Testopia?
EDIT 2:
In the meantime I think I've found a clue in the jenkins.log file in jenkins installation directory:
Exceptions like these occur:
INFO: TESTOPIA_TEST_SUITE_3 #13 main build action completed: SUCCESS
org.apache.xmlrpc.XmlRpcException: The requested method 'TestRun.get' was not found.
at org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTransport.java:197)
...
org.apache.xmlrpc.XmlRpcException: The requested method 'TestRun.get_test_cases' was not found.
at org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTransport.java:197)
Shall I insert the full stacktrace?
It looks like that plugin logs a fair amount of information, though not all of it to the build console output itself.
To debug further, you could try adding a new log recorder for the logger jenkins.plugins.testopia (with log level "all"), run a build, then refresh the web page for the newly-created log recorder to see the output.
You should at least see "Filtering for automated test cases" after connection, information about each test case found, and then log output for each iterative build step as it's run on each test case.
I got the similiar problem when I use python xmlrpc to commnicate with my bugzilla-testopia server.
I chekc the error code and find XMLRPC.pm under my bugzilla install location : "./WebService/Server/XMLRPC.pm".
I know the error was thrown by this sub function, which checks login status and forward to modules where the moduel.function must be in PUBLIC_METHODS:
sub handle_login {
...
if (none { $_ eq $method } $class->PUBLIC_METHODS) {
ThrowCodeError('unknown_method', { method => $full_method });
}
...
}
I don't know why but TestCase.get could not be found in PUBLIC_METHODS, so I just marked them as comment and then it works. You can do this quick way to make sure your client setting is correct. Then you should solve the "PUBLIC_METHODS" problem next.
I want to do remote debugging of Squish application.
I am following document at:
http://kb.froglogic.com/display/KB/Configuring+a+remote+squishserver
for the same.
Step 1 and Step 2 went well, even I able to see the logs in terminal from remote application.
But, the debug point is not hitting in Squish IDE. Even the debug view shows nothing though I have done the exact steps given at Step 3, even restart of Squish IDE didn't help.
Whether or not Squish stops at a breakpoint (I suppose that's what you meant when you wrote "debug point") is independant of where the squishserver process is running. You can verify that the remote server is used simply by launching a test: you should see some output in the console where squishserver is started about incoming network connections.
When running squish remotely you could add the flag: "--reportgen xml3.3,xml3report" This will create a report with all the information about your run. You can then import this report into squshIDE and use "vpdiff" tool to analyze your failure.
There is a command line tool called "vpdiff" which comes in SQUISHDIR/bin.
There is an article about it here:
https://www.froglogic.com/blog/analysing-test-reports-from-automated-executions-using-the-squish-ide/
I have a thesis project that requires a project log to be submitted along with my final paper. As part of that log I'd like to include the Bazaar revision log and all the messages that it contains but I'll need to have them in a printable format.
I was unable to find any export feature in the Bazaar Explorer tool but I hope it's still possible to do somehow. Any thoughts?
Thanks!
You can get log in the text format using command-line: bzr log > log.txt or via Bazaar Explorer with running All Commands dialog and select log command there and then copy the log from status window. Read the help for log command to find the appropriate options. You may want to use -n0 option and maybe --forward one.
For completeness, you can use the bzr-xmloutput plugin to get an xml version and then process that into exactly what you want.
I'm trouble shooting an SSIS package that is failing. When I execute the package it runs 1st step but fails at the second step with the message "Execution of the job "XXXX" failed. See history log for details, history log has very little information there. Is there a way to see an exact error or generate log file with meaningful information?
Thanks!
You should modify Logging in the package so that it logs all possible things and rerun the package to see where it is failing.
But before that, you should back up the package so that you can recover from mishaps.