How to check two excels in a validation? - ipaf

I'm trying to check two excels in a validation using excel tag of PAF while automation .Is it possible to validate two excels at the same time in pace automation framework?

The following code snippet is given below you can use for referral:
<activity id="Validations">
<excel excelPath="./excel1.xlsx" sheetName="Sheet4" resultsetVar="RSVar1" primaryKey="FirstName"></excel>
<excel excelPath="./excel2.xlsx" sheetName="Sheet5" resultsetVar="RSVar2" primaryKey="FirstName"></excel>
<validation valGroupIds="verify2ExcelsEquals" desc="TAG- validation; ATTRIBUTES- valGroupIds;" expResult="Verified the Excel files excel1 and excel2" ></validation>
</activity>
<valGroup groupId="verify2ExcelsEquals">
<validate resultsetVar1="RSVar1" resultsetVar2="RSVar2" condition="equals" passMsg="VERIFIED THE EXCEL FILES excel1 and excel2 ARE EQUAL" failMsg="FAILED EXCEL FILES ARE NOT EQUAL"></validate>
</valGroup>

Related

upload multiple Test cases at one time in ALM?

I'm trying to upload multiple Test cases at one go. How to upload multiple Test cases at one time in ALM ?
All flow files which you would upload should be updated with name attribute.
Make sure the src folder has a properties file named as “multipleFlows.properties” or you would have to create it.
Update the multipleFlows.properties file with all the flow ids and flow xml path that you would like to upload through ALMSync as mentioned below.
Ex: multipleFlows.properties file should contain as below format
flow1_id=flow1_xml_path
flow2_id=flow2_xml_path
flow3_id=flow3_xml_path
flow4_id=flow4_xml_path
Open the Run Configuration ALMSync >> Arguments tab and update the arguments as
createTestCase flow_map multipleFlows

Oracle APEX export PDF file name

I am exporting a PDF report from Oracle APEX using a Report Query defined in Shared Components. By default, the file name for the generated PDF is the Report Query name. Is there a way to customize the name? I need to include a timestamp in it, however I cannot find any solution. I am not using any external tool for report generation, and the layout is defined in XSL-FO.
Thanks for your help.
Create a PL/SQL process and use the following API:
APEX_UTIL.DOWNLOAD_PRINT_DOCUMENT (
p_file_name => 'myreport123',
p_content_disposition => 'attachment',
p_application_id => :APP_ID,
p_report_query_name => 'report1',
p_report_layout_name => 'report1',
p_report_layout_type => 'rtf',
p_document_format => 'pdf');
The above code assumes that your Report Query Name and Report Layout Name are report1
Note that you can change p_file_name to whatever you like.
If you are using XSLT 2.0 or XSLT 3.0, you can get the current time (not the modification time of the source document) using currentDateTime(). See https://www.w3.org/TR/xpath-functions/#func-current-dateTime
If you are still using XSLT 1.0, your XSLT processor might implement the EXSLT extensions for date and time. See http://exslt.org/date/index.html

How to use STANFORD PARSER from GATE

How to use Stanford parser from GATE embedded (using GATE through Java code). I currently use GATE_Developer_7.0 on my machine; i know that there is plugin for Stanford Parser in GATE but don't know how to use it using java code.
Thanks
The usual approach we always recommend for GATE Embedded is to build up your pipeline using GATE Developer, test it out and get it debugged by processing sample documents in the GUI. Once you're happy with the application, use "save application state" or "export for GATECloud.net" to produce a saved state that you can then load in your embedded code using the PersistenceManager. This will automatically ensure that all the necessary plugins are loaded and is generally much simpler and less error-prone than trying to build up your pipeline by hand in your code.
The BatchProcessApp example on the GATE website shows how you can load a saved application with the PersistenceManager, essentially it's
Gate.init(); // always the first thing you do
CorpusController controller = (CorpusController)PersistenceManager
.loadObjectFromFile(new File("/path/to/application.xgapp"));
Corpus corpus = Factory.newCorpus("myCorpus");
controller.setCorpus(corpus);
then for each document you want to process
Document doc = Factory.newDocument(....);
corpus.add(doc);
try {
controller.execute();
// code here to do stuff with the annotated document, e.g. extract
// annotations/features
} finally {
corpus.clear();
Factory.deleteResource(doc);
}

Is there any way to have Visual Studio ignore the <devdoc> tag when compiling?

Basically, I was attempting to keep all of my documentation in a separate file and use the <include> tag. This would let me keep my source code free of documentation clutter. I still wanted a way to have some developer notes about classes and members, so I used the <devdoc> tag. The problem is now Visual Studio adds my developer notes to the xml documentation file. Is there any way to not have it compile into the xml documentation?
/// <devdoc>This is an interesting Foo class</devdoc>
/// <include file="docs.xml" path='Doc/Member[#for="MyNamespace.Foo"]/*' />
public class Foo { ... }
Which resulted in:
<member name="T:MyNamespace.Foo">
<devdoc>This is an interesting Foo class</devdoc>
<Summary>Some summary for testing.</Summary>
</member>
I realize that Sandcastle is not going to use the <devdoc> class when it generates its documentation, but if I want to give intellisense information about my library I need to include the generated xml file. If it's impossible, it's not the end of the world, but I'm hoping that there is a way to exclude it to begin with.
I would create a simple console application that would be called from a post-build event. The application will remove all <devdoc> tags. It can be really simple. Just read the generated XML file and use regex like this:
using System.Text.RegularExpressions;
Regex regex = new Regex("<devdoc>(.|\n)*</devdoc>", RegexOptions.Compiled | RegexOptions.Multiline);
s = regex.Replace(s, string.Empty);
You can also use XmlDocument and its GetElementsByTagName method and then XmlNode.RemoveChild to remove the tags. But I believe regex would be more efficient.

SOAP faultcode list

I'm developing a magento script to import products from a XML file using the API and a SOAP wsdl connection.
I would like to know the faultcode list, I've been searching it for several days without luck, anyone know if there is one at all and where I can find it?
I need to handle the error codes to avoid the code to stop instead of just skipping the errors and continue importing what is correct.
At the moment I just discovered that the faultcode 101 is "Product not exists.".
Here's how to grab the list for your version of Magento. (I can't imagine this would be radically different between versions, but one never knows what's been done to a system)
Find all your api.xml files.
$ find app/code/core -name 'api.xml'
app/code/core/Mage/Api/etc/api.xml
app/code/core/Mage/Catalog/etc/api.xml
app/code/core/Mage/CatalogInventory/etc/api.xml
app/code/core/Mage/Checkout/etc/api.xml
app/code/core/Mage/Core/etc/api.xml
app/code/core/Mage/Customer/etc/api.xml
app/code/core/Mage/Directory/etc/api.xml
app/code/core/Mage/Downloadable/etc/api.xml
app/code/core/Mage/GiftMessage/etc/api.xml
app/code/core/Mage/Sales/etc/api.xml
app/code/core/Mage/Tag/etc/api.xml
Each file will have one or many <faults/> nodes which will contain the code and message.
<!-- File: app/code/core/Mage/CatalogInventory/etc/api.xml -->
<faults module="cataloginventory">
<not_exists>
<code>101</code>
<message>Product not exists.</message>
</not_exists>
<not_updated>
<code>102</code>
<message>Product inventory not updated. Details in error message.</message>
</not_updated>
</faults>
It's probably worth mentioning that the numeric codes aren't unique. Each "soap object" (unsure what to call these) defines its own.
<!-- File: app/code/core/Mage/Sales/etc/api.xml -->
<faults module="sales">
<not_exists>
<code>100</code>
<message>Requested order not exists.</message>
</not_exists>
<filters_invalid>
<code>101</code>
<message>Invalid filters given. Details in error message.</message>
</filters_invalid>
Good luck!

Resources