i am new to E-Test
We have a Product named X catering to the Financial domain for Supply Chain. The product is catering to a specified need for the CFO’s and organizations; it highlights and escalates the bottlenecks, which trap the working capital flow.
Product X is customized for Customer A’s needs (call it Product XA) and the reporting structure for the product highlights a facet of the cube which is at priority for the customer. Product X is again customized for Customer B’s needs (call it product XB) and the product highlight a similar facet of the cube (basically a dimension with which you wish to see the report e.g. area wise, salesman wise monthly summary OR reconciliation for Debit and Credit entries for the quarter etc.) but may have some cosmetic differences. In essence if you view these reports for XA and XB you will find visible differences in the layout and columns, filters, and of course DATA present within. Logically if you render a closer look the reports are similar. Their base structures would also be similar. I need to create a common script (or at least largely common scripts) for these products testing at functional level.
Can you provide technical help to do this task?
We also want to check data coming in the report against the DB.
How can we specify constraint at script level .g. text matching at script level not at page level?
How can we change the address of pages relatively for complete workspace?
Try using masking for the reports. This way you can eliminate certain areas of difference in the reports while leaving the basic common components available for validation.
You could also make this dependant upon which product-customer combination you are testing against.
eg, if Combination = XA then mask area1 is xcoords,ycoords
You can also combine this idea with the db info to extract the text from the area of interest and compare it to the db.
"Not every solution was derived to address an obvious problem" - Me (quite recently indeed)