It depends on the fix.

If the fix is something that hits low lying functionality used by the entire system, then the entire system needs to be regression tested.

If the fix involves the functionality of only one specific feature and has no interaction with any other feature, only that feature needs to be regression tested.

If the fix involves something trivial, then a smoke test level regression test is all that's needed.

I want to automate this page and click Ok Button, but the page is not displaying in HTML in Firebug and status is coming as "Waiting for ..."

In such cases how to automate the click without elements ? Please advice..

I often read the terms "testing method" and "testing paradigm", although they frequently seemed to be used synonymously. This question on Stack Exchange explains the terms in general, but I wonder how it is in the SQA world, where I found this blog post on software testing methodologies.

What constitutes a testing method, what a testing paradigm? What are concrete examples?

1. You can generate a JMeter HTML Dashboard Report from the .jtl results file like

   jmeter -g results.jtl -o /where/you/want/dashboard/to/be/generated
   

2. You can use JMeterPluginsCMD Command Line Tool in order to produce any report or graph type out of the .jtl results file. You can install JMeterPluginsCMS using JMeter Plugins Manager

   

Ideally, each project should have its own automation project (in the same or different repository of the SUT).

You can transform your framework in an extension to Cucumber. This way, people can get what they need for your general framework and implement what they need (even override your general behaviour).

zucchini is an exemple of such extension for Java. And there others for other languages [2][3]

I'm aware of the test automation pyramid, unit/integration/gui based automated testing. My question is, what does an integration test look like? I was always under the assumption for the likes of a login scenario we would use GUI automation to handle it, however after more reading I'm not so sure?

Option A

• Prep WebDriver & navigate to login
• Login as the user
• Assert that the user has logged in

Option B

• HTTP GET /Login
• HTTP POST Credentials
• HTTP GET /Index
• Assert that the user is logged in, perhaps their name is in the response body HTML?

Should we be always opting for Option B here? using something like REST-ASSURED and not using Selenium at all in this instance?

How do you decide which to do via the GUI and which via the Service/API layer like this? Obviously to me the API layer seems much more robust, changes to elements on the page will not break the tests etc but on the flip side, how will you know if the login button itself is properly functioning?

I have a MAC OSX native application. Some of the screens in this application is using Webviews.

My specific requirement is to automate this view using Selenium.

Questions that I have:

1. Is it really possible to use Webdriver to automate the Webviews in a native MAC OSX hybrid application?
2. If yes, can someone give an example script?
3. If it's possible to automate, how to identify the elements on this Webview?

I also tried with appium-for-mac for automating, but failed. (Seems like its a known issue as per: This post

My current setting for the webdriver setup is:

``` private WebDriver buildDriverInstance(String appiumForMacURL){

URL remoteAddress = null ;
try {
    remoteAddress = new URL(appiumForMacURL);
} catch (MalformedURLException e) {
    e.printStackTrace();
}

DesiredCapabilities desiredCapabilities = new DesiredCapabilities();
desiredCapabilities.setCapability("platform","Mac");
WebDriver driver;
driver = new RemoteWebDriver(remoteAddress,desiredCapabilities);
return driver;

}

<p>Any direction in this regard?</p>

We log the Jasmine test fails into a text file with a custom reporter. Afterwards we rerun the failed tests again only. If these still fail we report these fails at failures to research.

jasmine.getEnv().addReporter({
      specDone: async (result) => {
        if (result.status === 'failed') {
          fs.appendFileSync(SeleniumBrowser.getFailedTestsFile(), `${result.description}\n`);
        }
        await this.quit();
      },
    });

We use a script to rerun the tests from the command line. We are using jest -T , but with Jasmine I think you can use command-line arguments like --specs='tests/**/*.js' --grep="TestNameFromFile"

I once read an article (which I can't find anymore) that the a re-run strategy of three was the perfect number. Sometimes your infrastructure or network just hangs. After three times you are sure it is the test that is failing.

I would record the flakiness of these tests though and schedule a flakiness research once in awhile, but you do not want developers to waste adhoc time to re-run or research once in a couple of run errors. Some flaky test do succeed when run alone, these are the tests you do want to fix, but random single incidents should be ignored. keep in mind it could be race-conditions so do check them, but not instant adhoc

You should use the order that the company expects in the dropdown

That should be the order that makes most sense to your users based on their context

There is no 'best' way or simple standard other than what is most suitable for your situation based on the business requirements.

The most suitable approach will depend on many factors.
Context will also determine sort direction.

There are several general approaches:

• Alphabetic
  Most familiar in many cases. Can present issues for multiple languages

• Numeric
  Simplest to implement if data is displayed using a numeric index

• Temporal
  For example show today, tomorrow, next day-1, next day-2

• Context
  Uses data based on other characteristics that lend themselves to grouping items based on their characteristics, e.g. all 'saws' are listed under a 'saws' group even though their name may start with 'ragged saw', 'large saw', 'ban-saw', etc. This is often combined with Subgroups.

• Subgroups
  Sometimes there are major categories, e.g. country and then subcategories, e.g. state and to capture state it is helpful for users when the state dropdown has this tree structure. This method can include various of the other approaches for then sorting the data within both the main and children lists.

• Mixed
  Can be many different forms. One is that the top 'few' common options (1 to about 30 or so) are listed at the top and then a large number of less frequently used 'other' options are listed below them. You see this frequently used to for 'United States' as the top of a country list instead of at the bottom where alphabetic sorting would place it.

Are you or your senior knowledgeable about how users use the product for their context ?

try this:

driver.findElement(By.linkText("More information")).click();

driver.findElement(By.linkText("Go on to the webpage (not recommended)")).click();

Make sure you have enable protected mode for all zones under Internet Options -> Security.