I am trying to pass a link in assertion error message in the allure report for example:
assert expression, '...www.google.com...'
locally this isn't a problem as i see that in the terminal web addresses are formatted automatically to a URL however when i run the same test on a remote machine the generated allure report shows the same address as a regular string.
I tried using parselib.parse functions (like quote and urlparse) but it didn't help.
I also couldn't find any questions or answers to that anywhere online, the only option i found was attaching the link to the allure report but that is not my goal.
I would like to be able to click on the link appearing in the assertion error message as it may contain several links that i don't want to attach to the report itself.
Example report - marked in this report is the links i want to be clickable
Related
We had some projects deleted in Azure DevOps and we restored them, however all the widgets in the dashboard are broken. Is there a way to recover them or do we have to rebuild?
The dashboard does report across 3 projects, all of which were deleted then restored.
I receive a message about a / in a project title, but the project title I see does not have a /.
I have searched the User Guide and cannot seem to find the answer on this or one that explains the error message.
enter image description here
#wadezhou Cloud service. The error message says 'Widget error 400: The query configuration is invalid or number of work items returned exceeds the size limit.' (link above) I don't believe it is due to work items because I don't believe any work items have been added (these projects are just a proof of concept) and it was working before they were deleted. I have not tried to create a new widget - I will try that and see if it works and let you know. I'm not sure to tell if it's TFVC or git? It is Agile.
Here is a screenshot of the error where it mentions the / (when I go into the query):
error detailing /
When I try to create new widgets on the dashboard one works and one doesn't:
enter image description here
From what I can tell - it seems Git is the default type, and I have not changed it from whatever default would be.
In botium test report using mocha - reporter mochawesome we get Utterances wise result
ex -
Welcome/Welcome_input-L1
Welcome/Welcome_input-L2
Can we get actual conversation dialog in report. I have tried
"expandConvos": true,
"expandUtterancesToConvos": true
but i think it is not for reporting purpose. Can we expand conversation in report with request and response ?.
Botium CLI is using Mocha internally as a test runner. It supports all types of report formats supported by Mocha: https://mochajs.org/#reporters
Additionally, there is the mochawesome reporter included as well as a CSV exporter. Configuration is done with a positional parameter:
botium-cli run csv
Some reporters accept additional options, those can be specified with the --reporter-options switch
The rendering of the test output is up to the selected reporter - mochawesome is not in any way special to chatbot testing, so it doesn't support rendering of the conversation. If you want this kind of rendering, you will either have to code yourself (and make a pull request to the Github project), or use Botium Box
I have a legacy system that has a CMS server set up to generate Crystal Reports all from the same database. Users will input the required parameters in a front end application, which then passes it to the CMS to generate the report in a CrystalReportViewer.jsp page. The report titles as shown in both the CMC console and InfoView is as follows:
PersonnelDetailsA
PersonnelDetailsB
PersonnelDetailsC
After a recent update to the application (which did not touch on the Crystal Report functionality at all), users reported that they were unable to generate a report for PersonnelDetailsB (A and C were both working fine). The stated error message that they got was
Report source could not be retrieved from the state object
After some googling and trial and error on our development setup, I figured out that the error was caused by the CMS not being able to find the report requested, so my immediate, and actually only, hypothesis was that the report name my application passed to the CMS was wrong (the only way I've managed to reproduce the error). So I went and verified it in the production InfoView.
Turns out I was dead wrong. All the report names are correct.
As far as I know, nothing has changed with the set up of the CMS in production. The reports worked fine prior to our application update and I've verified that we did not make any changes in our application that would affect the Crystal Report functionality. In fact all the reports work perfectly in our development setup. Yet something clearly went wrong when we deployed to production. All 3 reports are in the same folder, and yet one of them cannot be found even when the correct report name is provided.
What am I missing here? What other way would cause the CMS to throw that specific error beside not being able to find the report in question?
I'm trying to deploy my crystal reports windows application project on clients computer.
the problem is I can't to load reports.
I installed CRRuntime_32bit_13_0_1 on client computer to solve the problem
but I encounter another error which appears when I try to load any of reports, the error is :
unhandled exception has occurred in your application, if you click continue, the application will ignore this error and attempt to continue. if you click quit, the application will close immediately,
when I click Continue button, my report loads without any data loaded.
what is the solution? the error detail is :
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
It sounds like the path to the data source is incorrect I would recommend ensuring that the path not only exists but has the right permissions.
thanks a lot,
I used manual addressing in assigning report file for my reportDocument.load() method
when program loads on client computer, address goes invalid.
the problem solved!
instad of using reportDocument and manual addressing I make new object from each report file (which haves .cs class) and assing it to crystalreportwiewer.reportsource:
Rad.ExecuteForms.Forms.Reports.CrystalReport1 noticeMainReport = new Reports.CrystalReport1();
noticeMainReport.SetDataSource(Main);
noticeMainReport.VerifyDatabase();
crystalReportViewer1.ReportSource = noticeMainReport;
Greetings!
I am using SSRS with MS SQL Server 2008 R2, which has the new feature of supporting shared datasets.
First, I created my shared dataset, and made sure that it worked correctly and had a good connection. That worked great.
Second, I created a new report (Let's call it "ReportSub"), and I had it use my shared dataset. The report works great.
Third, I created another report (Let's call is "ReportMain"), and I put a subreport object into the report and associated it with "ReportSub". Doesn't work. Instead, I get this error:
Data retrieval failed for the subreport, 'ReportSub', located at: /ReportSub. Please check the log files for more information.
Any ideas of what the problem may be? It will work if I use an embedded dataset, but I really need to use a shared dataset.
Thanks,
Currently, there is no way to Preview the subreport with shared datasource/dataset in BIDS.
Link: http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/74e51434-1d14-4fb1-9b1c-1a394c187b2f
I had this problem for "preview" only. As soon as I deploy this to Reporting Service server it starts working fine.
I had the same problem when previewing my MainReport. The SubReport preview works fine, but the MainReport preview produces the error "Data retrieval failed for the subreport".
The solution is not use shared dataset in the SubReport but an embedded daaset!
I have also observed that some changes in the SubReport are not taken over by the MainReport. So I had to close and repoen the project again.
I was experiencing this problem even after deploying. I discovered that I was prompting for datasource credentials in the subreport, but not in the main report.
After I made them both the same (prompt for credentials or set them both to use the provided credentials), the problem went away and I was able to preview.