Currently for any test run, I have to keep adding the options --keepdb -v2 to the testrun configuration as below snapshot
How to save this as default for next test run?
p.s.
The google search leads to limitted helpful post here.
Search on our stackoverflow site results 0 result; related suggestion leads us to this closer post.
Please try to update the template under Templates directory (under the last Test:... configuration on your screenshot)
Related
I'm attempting to add a badge to my GitHub repo showing the status of unit tests. I followed the guide, shown here, and produced the following change to my repo:
[](https://github.com/xefino/goutils/actions)
However, when I navigate to the repo's page on GitHub, I see that the action shows "No Status". I understand, from this question, that the name described in the workflow's YAML file has to match the URL, which mine does. So I'm having trouble understanding why I'm not seeing a status on the badge. Does anyone have any information on this?
I discovered the issue here. My URL was not actually correct, not because of some typo, but because the format had changed. So, doing this worked:
[](https://github.com/xefino/goutils/actions)
I want to send some diagnostic output to the default report.txt file.
In some posts it is shown that exceptions are logged to this report.txt file somehow (automatically or not?).
Also, I see in some samples that people do the logging with
System.Console.WriteLine(),
I've tried this, but still can't see it in the report file.
Could you tell me, how to achieve this?
I understand there is an option to create another log file and send it back with the result, but I think it would be easier to use this existing report.txt.
Thanks!
UPDATE: System.Console.WriteLine() works.
The reason why I didn't see the output was that my add-in failed to load.
So, it simply didn't reach this line of code.
Logging in Design Automation for Revit appbundles can indeed be done with System.Console.WriteLine. Anything sent to standard output will be capture in your workitems report.txt. For example.
The following code:
System.Console.WriteLine("Hello World!");
Will generate the following lines in the report.txt:
[04/23/2020 19:20:59] Hello World!
I have a question about jmeter reports.
I run my test plan in non ui mode and get csv, and html dashboard in Jmeter.
The problem is in html dashboard that is not informative enough, when I finished the Jmeter run, I enter the csv, and I can see all the steps and all the thread groups and for each step to see if is pass or No, and the error message.
The html dashboard reports not informative, I can see the top 5 errors, but not in which thread group they happened, moreover I want to see all the error and to see exactly where it is failed. Is their a way to display the whole csv as html? since all the reports are for performance and not give data about functional. after the run still need to enter csv and filter success row to failure, and check for error and assertions.
Is their any solution to see in reports the full picture of errors?
** my purpose is that when entering the html report the manual QA can see exactly the errors and in which step and in which thread group, exactly like in the csv. and all of them, without grouping, just the full row data
Provided pic of csv and html dashboard
[][CSV each step get a line with results]
[][dashboard not understand which error occurred in which test and not get full error results]
This "Top 5 errors" is hard-coded so it isn't something you can easily configure. There is report-template folder under "bin" folder of your JMeter installation where default report template lives, you can amend FreeMarker configuration starting from here
An easier solution would be switching to JMeter Ant Task which contains very simplified test report in HTML format with verbose error information on each and every failure, it should be a good substitution for you as manual QAs normally don't need performance-related metrics and charts. See Five Ways To Launch a JMeter Test without Using the JMeter GUI article for more detailed explanation and example configuration.
Did someone ever set up Zabbix to work with HP OpenView ?
Zabbix docs doesn't mention much information on that.
I know I have to create a media linked to a script.
In that script I have to use the opcmsg command but I don't understand the part which involves the database.
Can someone who ever experienced it drives me to the solution ?
Regards
You are missing media script doc. Parse input in your media script and process it with 'opcmsg'.
Try to find similar alert scripts (concept, not code) for your inspiration - https://www.zabbix.com/documentation/3.0/manual/config/notifications/media/script
And finally please publish your script with documentation (I recommend Github + Zabbix share).
Finally we have decided to create a media script which is writing output to a file.
Then that file will be monitored by a HP OpenView agent.
The steps are the following:
Create media script which is referencing your script :
In my case the script is named hpov.sh
The location of your script has to be referenced in your server config file (zabbix_server.conf) this way : AlertScriptsPath=/path/to/zabbix/scripts
Create an action which will be triggered on problems. Specify the macro you want in the first tab. The condition you want in the second one (leave as default). And finally set the third tab "Operations" like that:
You are free to change Users who are concerned
As the documentation says, link that media script to a user of your choice
That's it !
I don't know if this will help, but i enabled logging to a text file called test.txt on my C Drive.
Public Sub Main()
Dim rowsProcessed As Integer = 100
Dim emptyBytes(0) As Byte
Dts.Log("Testing, Test 1,2,3", rowsProcessed.ToString, emptyBytes)
Dts.TaskResult = ScriptResults.Success
End Sub
You have to go into the SSIS->Logging menu and tick checkboxes like a crazy checkbox-ticking-ninja to get this to work.
There are various checkboxes that have to be checked, and some of them only appear when you click on the script tasks, so it took me a while to figure this out:
First, enable your logging provider (that you have set up, right?) by ticking it on the Providers and Logs tab.
Then switch to the Details tab (which shows various events that you might want to log)
For the DTS.Log() method you need the ScriptTaskLogEntry event, but they only show up when you click on Script Tasks in the tree on the left.
So, click each of your Script Tasks in the tree on the left, enable it for logging, and then tick the Script Tasks event on the details tab.
Also make sure your logging provider is ticked for each script task
See also: http://msdn.microsoft.com/en-us/library/ms136131.aspx
This is an old question and #codeulike has answered it well but I would like to add a note about the logging behavior in debug mode, specially for someone new to SSIS or SSIS logging (like me) - Assuming you have all the configuration in place required for logging, if execute a selected task that you expect to log, it still will not log. Only if you execute (or debug) the entire package, then the logging will work.
If you are sure you have done configured everything correctly and still cant see your dbo.sysssislog in the database you selected, then check in the following
YourDatabase > tables > system tables
you can find your loggings there.
its my first time doing package loggings and configured everything correctly and could not see that dbo.sysssislog in the database it was supposed to do loggings and banging my head for half an hour when i realised it was in system tables of that particular database.
I realize that this question is rather old, but maybe it helps someone.
I ran into the same problem - while debugging in Visual Studio my textfile logging provider just did not write into the configured logfile.
My logfile was in the directory "project-directory/bin/development".
After changing the path to "project-directory-name"-root (eg. "/project-directory-name/test.txt" it worked.
I cannot explain this - it is just what I have observed.