Forum Discussion

javance's avatar
javance
Occasional Contributor
10 years ago
Solved

Firefox 38.4 released. As usual TestComplete does not support it.

There are no patches available for 38.4 ESR for any version of TestComplete including 11.2.  This is business as usual for TestComplete and you seem to think it's acceptable.  It isn't.

 

Firefox ESR channel is released on a schedule:  https://calendar.google.com/calendar/embed?src=mozilla.com_2d37383433353432352d3939@resource.calendar.google.com

 

Given the amount of money you charge for this product, it isn't unreasonable to expect you to keep on top of this schedule and release your patches in tandem.  38.5 ESR is scheduled for December 15.  Please make sure your patches are ready to go on that date.

  • Cucumber step definitions take a matcher, (some options - which we'll ignore for now) and a function. This example defines an anonymous function inline with the step definition:

     

     

    When('step matcher', () => {
      // function to run when the step matches
    });

     

     

    It is also possible to use a named function and pass the function to the step definition, e.g.:

     

    function stepFunction() {
     // function to run when the step matches
    }
    
    When('step matcher', stepFunction);

     

    You can define steps so that they will extract part of the step text and pass it as an argument to the function that Cucumber executes when it runs, e.g.

     

     

    When('step matches {string}', (theMatchedString) => {
    // function to run when the step matches
    });

     

     

    You can of course extract a named function which takes an argument and pass that to Cucumber:

    stepFunctionWithArgument(theMatchedString) {
    // function to run when the step matches
    }
    
    When('step matches {string}', stepFunctionWithArgument);

     

    If we look at your example you are calling the confirmSheetCreated function when you are creating the step definition, not when you are executing your Gherkin specification.

    You probably need to capture the arguments you want to pass to the function in the step matcher, something like:

    async function confirmSheetCreated(folderName,sheetName) {
        await this.page.waitFor(1500);
        let sheetExists=await this.sheetExists(folderName,sheetName)
        await this.page.isTrue(sheetExists);
    }
    
    // this will match: I confirm in folder: "Revenue" new sheet created: "Test Sheet 1"
    // and pass the folderName and sheetName parameters at runtime
    Then( 'I confirm in folder: {string} new sheet created: {string}',{ timeout: 5*1000 },  confirmSheetCreated);


    Alternatively, if those folder and sheet details are always the same you could push them into the function:

    async function confirmSheetCreated() {
        await this.page.waitFor(1500);
        let sheetExists=await this.sheetExists('Revenue','Test Sheet 1')
        await this.page.isTrue(sheetExists);
    }
    Then( 'I confirm new sheet created',{ timeout: 5*1000 },  confirmSheetCreated);

     

7 Replies

    • TanyaYatskovska's avatar
      TanyaYatskovska
      Icon for Alumni rankAlumni

      Hi Javance,

       

      As far as I know, our R&D team always creates patches to allow TestComplete to work with the latest browser versions. I think the patch for Firefox 38.4 ESR will be available soon.

       

    • javance's avatar
      javance
      Occasional Contributor

      Thanks for the link to support.  I've submitted a request.  But still, this shouldn't be a support issue.

       

      If tests are being run daily, of course there is an immediate need. 

       

      This is a known, scheduled event.  Mozilla has a 6 week release cycle and their release schedule is public.  TestComplete should be releasing patches in tandem.  See above.

       

      The amount we're paying annually for license fees makes this sloppy coverage unacceptable.  This happens every single time there is a Firefox release.  Every 6 weeks.  Fortunately TestComplete is now working with IE 11 again after failing to work with IE 11 for several weeks due to a Microsoft security patch.  Otherwise I would be completely dead in the water and requesting a partial refund for the time during which the software was unusable.

       

       

       

       

       

       

      • javance's avatar
        javance
        Occasional Contributor

        I submitted a ticket and received a response that a version of Firefox that I am not using and did not ask about has patches for a version of TestComplete that I am not using and did not ask about.

         

        It is November 9 - six days without support for the corporate recommended version of Firefox - ESR 38.4 - in the latest version of your product - 11.2.  I expect someone to contact me now and tell me how this is going to be made right.