Go by the word. Test Plan means we are planning for particular scope. We have to test on given environment withing given time frame defined in Test Plan. While the strategies will be common at organization level which is high level description about testing, what kind of testing and where etc.

Please check the below Solution:

Step 1:

Get the Class ID from IE > Tools > Manage Add-ons

Step 2:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Ext\Settings{47833539-D0C5-4125-9FA8-0819E2EAAC93}] “Flags”=dword:00000001

Note: 0 is for enable and 1 is for disable.

I use Selenium WebDriver in Java and I need to configure Safari and Opera browsers. For Opera almost work properly but I need to set Binary

System.setProperty("webdriver.opera.driver", dirPath + "\\src\\test\\resources\\operadriver64.exe");
OperaOptions op = new OperaOptions();
op.setBinary(new File("D:\\Program Files\\Opera\\47.0.2631.55\\opera.exe"));
driver = new OperaDriver(op);
driver.manage().window().maximize();
driver.get(baseUrl);

Is it possible to skip line setBinary and still working?

Second question is about Safari web browser. I use this code:

System.setProperty("webdriver.safari.driver", dirPath + "\\src\\test\\resources\\SafariDriver.safariextz");
driver = new SafariDriver();

and occurs error org.openqa.selenium.WebDriverException: SafariDriver requires Safari 10 running on OSX El Capitan or greater. Is it possible to run tests on windows 7 using Safari?

I have one API, who gives a dynamic response in terms of number arrays. I want to execute next API based on the count that I got in the first API.

API 1 Response:
{ 
  "Test 1": [
{Array 1},
{Array 2},
{Array 3}   ]
}

API 2 Request:
{Array 1},
{Array 2},
{Array 3} 

I tried If controller but my API exectuing one time only though i have 3 array.

First off, with pen testing you will want to ensure all aspects of your application are tested. This includes authenticated login and non-authenticated login. If you are simply spidering the application to find all the URLs then login and try as that will ensure successful connection to all the URLs. If you are pen testing via spidering and running additional tests on each URL then you will want to do both authenticated and non-authenticated tests to ensure each behaves the way it should.

Spring generates things based on the way it's setup and therefore will likely have a bigger structure than what appears to be on the surface. This will likely increase spider time as the spider will reverse engineer the rendered structure to locate all the URL paths that may exist. As the spider finds hidden things it will go down every possible path to locate URLs in the application. This takes time and 10 min. although lengthy, seems reasonable depending on what all is running at the same time via ZAP. URLs must be found, determined viable or not and many checks on these URLs are performed which requires network communication for the handshake checks of each URL. I'm not positive about ZAP settings, but you might be able to adjust some of the settings in the spidering to only check a few things instead of whatever the default settings are. If there are 3 checks on a URL and the handshakes takes 5 sec. now you could be at 15 sec. per URL.

Based on what I'm reading in the question there could be a performance improvement task on the application that you might want to look into. It really depends on the specifics though and if the spider is taking a longer time on the spring arch URL setup and not the user facing GUI then that performance hit likely will never affect the user experience.

Also, consider running the spider in headless mode to take out the GUI rendering time and speed up the process. If this part makes it alot faster then you might also want to look into boosting performance in your GUI rendering.

If you'r company is hiring for QA Role & you have planned for a Practical test round of the QA candidates then-

If you are looking for MANUAL TESTER (QA):

• Prepare a Demo link of your any application which is having some defects. Assign this link to the candidates for finding Bugs.
• Ask him to make a DEFECT REPORT; so that you will easily test his/her defect reporting style or way of reporting.
• Also, you can easily test his/her thinking capability, positive-negative scenarios, deciding severity/Priority..etc.
• You can also assign writing TEST CASES on the same application where you will be able to check his way of writing Test Cases & reporting.
• ask some Database queries (SQL/MYSQL) to check a database knowledge.
• If you are looking for strong analytical/problem-solving candidates then again you may provide some analytical/problem-solving questions like- puzzles, problems on mirror images etc.
  for Example -

If you are looking for AUTOMATION TESTER (QA):

• Ask him to do complete Selenium setup (installation) required to start selenium project.

• Ask him/her to design project structure in eclipse IDE or Framework design

• you can also provide the same test link of your application for automating small module using java & reporting tools like TestNG...

• provide some JAVA programs where you can easily check their programming knowledge.

• ask some Database queries (SQL/MYSQL) to check a database knowledge.

Finally, You can not check his practical knowledge in 2 or 3 hrs practical test, you have to focus on his/her long term goals, candidates analytical, problem-solving skills, Manual testing concepts, Programming concepts, personality, his attitude, communication skill and many more things.

Looking for an XPath for a webpage where after every booking a Rel# generate. Need to validate the Rel# is saved in a different tab or not.

So the HTML page says:

I tried with the given xpath

"//*[@id="summaryDiv"]/table[4]/tbody/tr[2]/td[1]/b[2]"

also with "//b[contains(.,'Rel#:')]/parent::td"

But every time it returns the value "b" but not any relation numbers.

What should I use identifying the correct XPath for Rel#?

Why your attempts failed:

• your first attempt:

  WebElement button = driver.findElements(By.cssSelector("button[@class='button' and @type = 'button' and @onclick = 'shippingMethod.save()']")).get(3);    button.click();
  

  The CSS selector is not valid - attributes should not start with @, and is not used to join conditions in the CSS selectors.

• your second attempt:

  driver.findElements(By.xpath("//div[@oneclick,'shippingMethod.save()']//button[contains(text(),'continue')]"))).click();
  

  Here the problem is in the button[contains(text(),'continue')] part - the text() of your desired button is actually empty because that continue you are looking for is on the deeper depth level, button[contains(.//text(),'continue')] would've worked.

• your third attempt: again, not a valid CSS selector

And, overall, I would not go the way of getting the button by an index - relying on that it is the 4th, or the last button on the page, because in this case you make your locator dependent on the buttons positions on the page - simple layout changes will break it.

Solution

There are multiple ways to get to the desired button, probably one of the simplest would be to check the title attribute to be Continue and for onclick to contain shipping:

driver.findElement(By.cssSelector("button[title=Continue][onclick*=shipping]"))

Or, even easier would be to check the id of the parent container element:

driver.findElement(By.cssSelector("#shipping-method-buttons-container button"))

I am a bit stuck while automating SOAP service . I have below url and request xml :

Background:

url 

 Scenario: soap 1.1

request
 """ 


When soap action '********'
Then status 200

After running it through Karate i am getting below issue :

18:07:52.413 [pool-1-thread-1] ERROR com.intuit.karate - 
status code was: 500, expected: 200, response time: 1088, url: :
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Body><s:Fault>
<faultcode xmlns:a="http://schemas.microsoft.com/ws/2005/05/addressing/none">
a:ActionNotSupported</faultcode><faultstring xml:lang="en-US">

The message with Action '*********' cannot be processed at the receiver, 
due to a ContractFilter mismatch at the EndpointDispatcher.
This may be because of either a contract mismatch (mismatched Actions between sender and receiver)  
or a binding/security mismatch between the sender and the receiver.
Check that sender and receiver have the same contract and the same binding
(including security requirements, e.g. Message, Transport, None).
</faultstring></s:Fault></s:Body></s:Envelope>

Please help!

You can/should utilize the SelectElement class which conveniently abstracts away the "select-option" HTML blocks:

var distance = driver.FindElement(By.Id("distance_adv"));
var selectDistance = new SelectElement(distance);

selectDistance.SelectByText("10 miles");

This is a follow-up to What makes a good selenium locator?

Motivation

I've been thinking about detecting the complexity of CSS selectors statically.

The scope I'm working in is both test-automation and web-scraping where choosing a reliable CSS selector is important to be as less dependent on UI/markup/layout changes as possible.

Currently, I'm able to check the "depth" of a CSS selector by parsing it via css-selector-parser and simply counting the number of nodes. If the number of nodes is more than 5 I'm concluding that this is a potentially complex CSS selector. The reasoning behind this is that, the more nodes a selector has in the path, the more dependent on the HTML structure of the page it is - the more fragile it is. For instance, this CSS selector would be considered "fragile" (6 nodes):

.content > table > tbody > tr:nth-child(2) > td.cell > input#email

Eventually, I'm thinking to develop a metric where each selector would get a special "score" value that would a measurement of a selector being more solid/durable. Inspired by famous code complexity metrics, like Cyclomatic Complexity or Maintainability Index.

Question

What parameters would you consider to determine if a CSS selector is resistant to a change? What makes a reliable CSS locator?

Thoughts

• usage of layout-oriented bootstrap classes inside CSS selectors would be a signal of a bad locator
• implementation-specific classes and attributes would make a selector less reliable. (e.g. in case of AngularJS - ng-scope or ng-binding classes)
• using id or name attributes would probably be desirable