I am using dateLabeller in Cruise control .net for labeling purpose.
<labeller type="dateLabeller">
</labeller>
it is working fine for me, each time build label is incrementing every time.
But i also want to add some text before date so i have use following code
<labeller type="dateLabeller">
<yearFormat>QAT-0000</yearFormat>
<revisionFormat>0000</revisionFormat>
</labeller>
Now each time a fore build is trigger same label is generating.
How can i fix this problem
Thanks in advance.
Use the format values just as you would use them in Int32.ToString(String). Find information on Custom Numeric Format Strings here.
So this should fix it:
<labeller type="dateLabeller">
<yearFormat>'QAT-'0000</yearFormat>
</labeller>
Update: I took a look at the sources and found out that dateLabeller isn't capable of processing non-numeric labels since the label of the last successful integration is parsed into a System.Version object.
Related
In IS version 7.10.38.9-LTS price list import converter has hardcoded US locale value for name and description fields.
Resulting backend for German language looks:
Is this issue meant to be localized in future versions?
So that we can choose option to adapt either CSV files or override/create own converter template.
PriceListCSVConvert.isml:
<description xml:lang="en-US"><isif condition="#isDefined(data:PriceList_Description)#"><isprint value="#data:PriceList_Description#"></isif></description>
Thank you for bringing this issue to our attention.
A bug ticket has been created, and we will evaluate it later this week.
As far as I know, it has been like this for a very long time and we never heard about issues with it.
If I interpret the other csv templates correctly, it is only possible to import an attribute (for example price list description) in exactly one locale and you would like this locale to be customizable, is that correct?
I want to have an option on the cucumber report to mute/hide scenarios with a given tag from the results and numbers.
We have a bamboo build that runs our karate repository of features and scenarios. At the end it produces nice cucumber html reports. On the "overview-features.html" I would like to have an option added to the top right, which includes "Features", "Tags", "Steps" and "Failures", that says "Excluded Fails" or something like that. That when clicked provides the same exact information that the overview-features.html does, except that any scenario that's tagged with a special tag, for example #bug=abc-12345, is removed from the report and excluded from the numbers.
Why I need this. We have some existing scenarios that fail. They fail due to defects in our own software, that might not get fixed for 6 months to a year. We've tagged them with a specified tag, "#bug=abc-12345". I want them muted/excluded from the cucumber report that's produced at the end of the bamboo build for karate so I can quickly look at the number of passed features/scenarios and see if it's 100% or not. If it is, great that build is good. If not, I need to look into it further as we appear to have some regression. Without these scenarios that are expected to fail, and continue to fail until they're resolved, it is very tedious and time consuming to go through all the individual feature file reports and look at the failing scenarios and then look into why. I don't want them removed completely as when they start to pass I need to know so I can go back and remove the tag from the scenario.
Any ideas on how to accomplish this?
Karate 1.0 has overhauled the reporting system with the following key changes.
after the Runner completes you can massage the results and even re-try some tests
you can inject a custom HTML report renderer
This will require you to get into the details (some of this is not documented yet) and write some Java code. If that is not an option, you have to consider that what you are asking for is not supported by Karate.
If you are willing to go down that path, here are the links you need to get started.
a) Example of how to "post process" result-data before rendering a report: RetryTest.java and also see https://stackoverflow.com/a/67971681/143475
b) The code responsible for "pluggable" reports, where you can implement a new SuiteReports in theory. And in the Runner, there is a suiteReports() method you can call to provide your implementation.
Also note that there is an experimental "doc" keyword, by which you can inject custom HTML into a test-report: https://twitter.com/getkarate/status/1338892932691070976
Also see: https://twitter.com/KarateDSL/status/1427638609578967047
I am re factoring large sets of tests in SoapUi.
Is there a way to automate creation and renaming of test cases/test steps through Groovy?
Thanks.
Possibly not what you're looking for but I've had some success manually editing the test suite xml using find and replace in a text editor. You need to be careful and make sure to back up a copy.
You can run Groovy code within SoapUI using SoapUI Groovy Console plugin. This way, you can change any property you want programmatically (within API constraints of course).
As for technical details on how to solve your actual problem, I can only refer you to this blog post and SoapUI's javadoc. Based on the blog post, you need to figure out what's given to you, and based on the API, you need to figure out how to achieve what you need.
In my case, I started with my project being bound as a project variable, and moved on from there.
There is really not so much information in the question about what you really need to achieve, but given the little you provided, one way to go would be to directly modify the soapUI project XML file. I have done this with some success in the past. The last I used soapUI, it UI did not come with massive refactoring functionality.
I'm trying to automate a process for our documentation team. They have a pretty big batch of framemaker files across several books and use RoboHelp to generate EclipseHelp for two different versions of our project.
Each framemaker file has the appropriate tags set to indicate which version a particular piece of documentation applies to. Currently the writers modify the conditional build expression to specify the correct set of tags and run File->Generate->EclipseHelp each time. I can run the generation process just fine, but I can't figure out how to change which tags it's using.
I've read through RoboHelp's scripting guide and the only references I can find to Conditional Build Tags is the ability to create and delete them. I can't find any references to Conditional Build Expressions. Does anyone know any way to modify it from a script? Alternatively, if someone can suggest a different way of organizing RoboHelp/Framemaker that is more conducive, I'm all ears, though I have basically zero familiarity with either.
The Conditional Build Expression forms form of your EclipseHelp Single Source layout. As such your script needs to refer to the tags there.
I'm going to answer with what I found - even though it's only a partial answer - just in case it can help someone, or possibly give someone enough to figure out a more proper answer.
Basically I found that each Single Source Layout has a corresponding *.ssl file. If your layout is called OnlineHelp, it will be (in my experience) OnlineHelp.ssl and will be in the same directory as your .xpj file. The ssl file is just a bunch of xml and has some number of sections. One of the sections will have the same name as the content category where you would go in the UI to change the Conditional Build Expression. In that section is an element named "BuildExpression". Set that to whatever you need and reopen your RoboHelp project. It's a bit of a hack, but I set up a groovy script to do that before running my ExtendScript and it gets the job done.
I have a NSMutableAttributedString, Now I want to add Link to some portion of the text. how can i add a link to the text so that when the user touches the text i can fire some actions. I'm working in iOS 4.2
Thanks in Advance.
Shinto
I did a library a few months back that dealt with that exact use case. However, I had to re-use it last week and found out that CMTextLabel isn't very user-friendly.
https://github.com/pothibo/CMFramework/tree/master/CMKit/RichText
You could have a look at it. If you decide to use it and refactor some of it to make it easier to use, send a push request and I'll merge it.