DanH
Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
Tests for InstallShield wizard stopped working
Hello, I’m having a problem with InstallShield wizard. I have been using this in tests which have been running fine for over two years to uninstall and install versions of the desk top application to be tested. The test scripts have stopped working as they no longer recognise the controls in the InstallShield wizard, the Modify, Repair, Remove options and the Next button etc. I have tried recording a fresh test script to check if my old scripts have a problem, but when I run the script just recorded it has the same issue: not recognising any of the controls in the InstallShield wizard. I thought I might have somehow messed up the name mappings, so I tried writing a script from scratch using the name mappings I had for the wizard… again, none of the controls were recognised. I then tried deleting the name mappings and setting them up fresh… again, none of the controls were recognised. Does anyone have an idea how I might try fixing this? Thanks in advance, DanSolved1KViews0likes2CommentsCheckpoints on recordsets with multiple tables
Hello, I have a problem testing the data returned by a SQL stored procedure. I have set up DBTables for stored procedures which return a single table with no problem; however, I need to check a number of stored procedures which return multiple tables. I can't find any obvious way to do this in TestComplete. When I set up a DBTable to run the stored procedure, only the first of the tables in the recordset is saved. Would the best way to procede be to run the stored procedure and then create a DBTable for each table in the recordset returned? Any ideas on the best way to achieve this would be gratefully received.Solved1.2KViews0likes4CommentsRe: Attach report to Azure DevOps pipelines for every test case
Hi JuliaBernikova , I have a similar requirement to jlrosalesp : If I want to get the patch you mentioned. Could you let me know what I should ask the support team for: Alternatively, as my need isn't that urgent, would the next version of TestComplete will be out quite soon, in which case I could simply wait for the next version. Thanks in advance, Dan2.3KViews0likes2CommentsRe: How to map multiple instances of the same form
Hello there, Thanks for your suggestion, I’ve now managed to sort the issue out. After trying to save the form frmInvoice as an object in Stores for both Purchase Invoice and Purchase Credit Note and drilling down into its properties to figure out which one to use… then realising that, whilst it might work, would be very cumbersome, I followed your advice simply copying the mapped objects and adding a filter to the properties. I opened up my name mappings and copied the mapped object frmInvoice. I then renamed one version frmInvoiceForPI, and one frmInvoiceForPCN. I then simply added a property to filter by the FormCaption to be either “Purchase Invoice” or “Purchase Credit Note”. It is now easy to distinguish between the two instances of the form when writing code: The different mapped objects also seem to be correctly used when simply recording KeyWordTests. Thanks again, Dan1.1KViews1like0CommentsHow to map multiple instances of the same form
Hello, I've got a bit stuck with a test which runs two instances of the same form. The situation is: We have a Winforms application which has a form frmInvoice, this is used for a wide range of invoice types. On the whole this isn't a problem as I can simply use the mapped frmInvoice for which ever type of invoice I am testing. However, there are a number of tests where an instance of frmInvoice will open up a fresh instance of frmInvoice whilst remaining open, e.g. an instance dealing with Purchase Invoices can open an instance for Purchase Credit Notes. I have recorded a test which does this but it will not play back correctly as when the code to enter text into a control on the second instance of frmInvoice (Purchase Credit Note) is hit, the control on the first instance of frmInvoice (Purchase Invoice) is the target. I have tried mapping the two instances of frmInvoice, as e.g. frmInvoicePI and frmInvoicePCN, but I have not been able to do this. If I try to map a fresh instance of the form, TestComplete says it is already mapped. I have tried looking in the Object Browser: I can see both instances of frmInvoice, but again, I cannot change their mapping to distinguish between them. Would anyone have an idea how I might start distinguishing between the two instances? Thanks in advance, DanSolved1.2KViews0likes3CommentsRe: Ordering of Tests in Azure Pipeline
Hi Tanya, Thanks for getting back. The problem I have is the ordering of the tests when run using a Test Plan in an Azure Pipe Line: There's no problem running them from a Test Complete project. I have a number of Test Complete tests, which I have linked to Test Cases. The test cases are added to a Test Plan, which is then run in an Azure Pipeline. These tests log on the a test application, import various data, enter some transactions and then close the application. If I have the Test Cases in one Test Suite in the test plan, arranged in the correct order, they will run fine. If I split the tests cases into different suites, covering different functionalities, the order the tests are run in breaks down. In the attached screen shot, I have the tests arranged in the Test Suite "Start Prime and Log In to Regression Test data". If I run just this Test Suite in the Pipeline, everything works. If I include the Test Suites "Import Ledgers For Accounts", "Cribsheet Advanced Test Cases" and "Close Down" in the Pipeline (obviously getting rid of any Test Cases which would be duplicated from "Start Prime and Log In To Regression Test data"), the first test cases of the first Test Suite runs, starting the application, followed by the first test case of the last Test Suite, which closes the application, so all of the tests in the middle fail. It's not a major problem as I can get round it by simply having all my Test Cases in a single Test Suite. I was just wondering if it is possible to split the functionality into different Test Suites, and still maintain the order I want. I hope that makes sense. Dan2.6KViews0likes1Comment