I was using following combination:
Appium : 1.6.5
Selenium : selenium-java-3.3.1
Appium Java Client : java-client-5.0.3
I downgraded the Appium client to:
Appium Java Client : java-client-5.0.0-BETA6
and the problem was solved.
I am not aware how/where to raise the issue of the version incompatibility issue.
I've created a very complex script using Python3 and YAML (I keep all the configurations in YAML) that in effect tests all potential file downloads for my environment. Sort of end to end test. Due to specific patenting behind, I can't share too much of code, but I am having around 37 different property combinations that download a different file, and each file can be downloaded as zip/gzip, or CSV/XML, so technically 37 X 4 is the total number of my files. To make it "simpler", I need to check that file with license key for combination 1, works only for 1, not for 2-37, and with it we are growing to a relatively big number of tests, currently around 380 in the script, 70ish being happy path tests, and the rest negative tests.
This script was so far run manually, and I'm now trying to convert it and automate with Jenkins, where I'd need to print out some nice report.
I have the following script structure in one big .py file (760 lines):
the method that executes a single test that then compares calculated MD5 from downloaded file and MD5 that is served from the server
def executeTest(testName,conf, compareFlag="", fromThread=""):
if compareFlag=="Compare":
testPrintableName = getTestName(conf, testName)
urlForFile = testUrlBuilder(conf, testName, "")
urlForMD5 = testUrlBuilder(conf, testName, "MD5")
if printHeadersAndPaths:
print (urlForFile)
timeDlStart = time.time()
filePath = getFile(urlForFile, "")
timePassed = time.time() - timeDlStart
#print (timePassed)
if printHeadersAndPaths:
print (urlForMD5)
md5Path = getFile(urlForMD5, "")
#print(filePath)
#print(md5Path)
if ((filePath == "Site Maintanance") and (md5Path is not None)):
print(testPrintableName + " Attempted to get file from site under Maintanance")
elif ((filePath is not None) and (md5Path is not None)):
if ((filePath == "Invalid Index Attempt") and (md5Path == "Invalid Index Attempt")):
print(testPrintableName + " Attempted to get wrong file with license for different Index type")
elif ((filePath == "Invalid Licence Attempt") and (md5Path == "Invalid Licence Attempt")):
print(testPrintableName + " Attempted to get wrong file with invalid licence (eg Beta licence to get Alpha file)")
elif ((filePath == "Invalid LicenSe Attempt") and (md5Path == "Invalid LicenSe Attempt")):
print(testPrintableName + " Attempted to get wrong file with invalid license (eg Beta license to get Alpha file)")
elif ((filePath == "Invalid Key Attempt") and (md5Path == "Invalid Key Attempt")):
print(testPrintableName + " Attempted to get wrong file with license for different File Type")
elif ((filePath == "Site Maintanance") and (md5Path == "Site Maintanance")):
print(testPrintableName + " Attempted to get from site under Maintanance")
elif ((filePath == "Nothing") and (md5Path == "Nothing")):
print(testPrintableName + " Attempted to get special data - where we return Nothing")
elif ((filePath == "Invalid License Gama At Alpha") and (md5Path == "Invalid License Attempt At Gama")):
print(testPrintableName + " Attempted to get Gama Data with wrong license")
else:
cal = calculateMD5(filePath)
ff = readMD5fromFile(md5Path)
if (cal.strip() != ff.strip()):
print ("Test "+ testPrintableName + "MAYBE FAILED - Calculated MD5 " + str(cal) + " does not match the one grabbed from file " + str(ff) + fromThread)
else:
print ("Test " + testPrintableName + " PASSED " + lastModifiedComparedToNow(lastModified, requestTime) + " in " + str(timePassed) + " seconds " + fromThread)
else:
if (filePath is not None and filePath != "Invalid Index Attempt"):
print ("Test "+ testPrintableName + "FAILED - " + "File was not downloaded properly " + fromThread)
if (md5Path is None and md5Path != "Invalid Index Attempt"):
print ("Test "+ testPrintableName + "FAILED - " + "MD5 file was not downloaded properly " + fromThread)
else:
pass
a load of methods that execute set of tests by name grouped in meaningful methods
def happyPathsPOIMaps(conf):
executeTest("POIMapCsvCommaZip", conf, "Compare")
executeTest("POIMapCsvSemicolonZip", conf, "Compare")
executeTest("POIMapCsvPipeZip", conf, "Compare")
executeTest("POIMapCsvXMLZip", conf, "Compare")
executeTest("POIMapCsvCommaGz", conf, "Compare")
executeTest("POIMapCsvSemicolonGz", conf, "Compare")
executeTest("POIMapCsvPipeGz", conf, "Compare")
executeTest("POIMapCsvXMLGz", conf, "Compare" )
Each test (again, coming from YAML) contains all the parameters used in building URL for certain file type, that is then tested. Tests in YAML look like this:
#format: 'testName,environment,licenseNameToTest,serverUrlExtendionToUse,CompressionFormat,FileFormat,DataFileType,MD5,Date'
POIMapCsvCommaZip: '"Test Get POI Map",testsrv,POIMap, getPOIMap, zip,xml, , '
YAML contains all servers and test combinations, and it's currently at 500 lines.
And now, finally, my questions:
I'm open to suggestions, this does the job at the moment, but I have a feeling that it is overly complex and that there must be a way to make it simpler. Maybe separate methods that are tested in a separate file?
Thanks in advance for not closing it as not constructive enough.
Yes, it would. I like teams that execute exploratory testing in pairs, I think it is easier to write charters, create mind-maps and decide on heuristics together than alone. It will keep you sharper, you will go faster in executing and analysing the results.
I would like to find answers on the following questions during an interview:
Seeing how someone would approach a pair-testing session is worth a lot. It is about communication and test design. Also, you will notice if someone is a quick learner. Can they lead the session and get some results while working together with someone else. How do they respond to critical feedback during the session.
Exploratory testing sessions are time-boxed, making it a great candidate for a second interview test. You can perform it with a time-box of let's say 45 minutes and work with a tester colleague. Afterwards, review the results together with the hiring manager. Giving the candidates room to explain what they would do differently next time for example. Resulting in an interview of around 1.5 hours, which I think would be acceptable.
Alternatively, I would do pair-programming of test automation on a simple application. Just like I would always do a pair-programming interview for developers.
I want to grab everything within this div with an id of "storytext":
<!-- END ID="STORY-META" CLASS="STORY-META" -->
<div id="storytext" class="storytext storylocation linkLocation">
<p>NPR's Ari Shapiro talks with <em>Washington Post</em> reporter David Weigel about the conspiracy behind Democratic National Committee staffer Seth Rich's murder last summer and how fake news is still spreading.</p>
</div>
<div class="transcript storytext" aria-label="Transcript">
<b class="icn-story-transcript-wrap">
<b class="icn-story-transcript"></b>
</b>
Trying to grab this div:
public void init(Properties p) {
log.info(p.toString());
String url = p.getProperty("url");
String tagNameString = p.getProperty("tagNameString");
WebDriver driver = new FirefoxDriver();
driver.get(url);
driver.manage().timeouts().implicitlyWait(9, TimeUnit.SECONDS);
String pageSource = driver.getPageSource();
log.info(pageSource);
log.info("done");
log.info(tagNameString);
List<WebElement> listOfWebElements = driver.findElements(By.tagName(tagNameString));
log.info(listOfWebElements.toString());
}
Execution log:
window.onload = (typeof window.onload != 'function') ?
loadChartbeat : function() {
oldonload();
loadChartbeat();
};
})();
</script><script language="javascript" type="text/javascript" src="https://static.chartbeat.com/js/chartbeat.js"></script></body></html>
Jul 12, 2017 8:11:59 PM net.bounceme.dur.web.selenium.Scraper init
INFO: done
Jul 12, 2017 8:11:59 PM net.bounceme.dur.web.selenium.Scraper init
INFO: storytext
Jul 12, 2017 8:12:12 PM net.bounceme.dur.web.selenium.Scraper init
INFO: []
thufir@doge:~/NetBeansProjects/selenium$
whether to iterate, parse or persist. Playing with Selenium.
I am trying to find out XPath for this "Sign Out" button, can anyone help me?
We have both automated and manual tests for our actively developed application. A regular Jira workflow in our case is something like this:
Open -> In Development -> In Testing -> In Automation -> Resolved
From release to release, we are usually behind in automating the new features and fixes. But, we do, of course, cover the new features with manual tests and test scenarios.
This leads me to the actual question:
How do you keep track of what functionality/features/screens/pages/fixes of the application are covered by an automated test and what are not?
The ideal situation would be to be able to see, at any given point in time, what parts of the application are covered with manual tests scenarios and what parts are covered with automated tests. Currently, we are trying to use a simple spreadsheet in a "checklist" style format, but it is not readable, scalable and maintainable at all.
A lot of stuff covered by OWASP applies to applications as the line between desktop app and web app blurs. Things like SQL injection, command injection, object injection to name a few injection attacks. I once tested a .Net MVC app by uploading a PHP file and tried to see if the code was executed or presented as raw text when viewed.
As far as tools you could try a free product like Metasploit but the learning curve is steep.
QA closes bugs where I work. In most cases, bugs are closed without mentioning any details about the root cause. The only info given is one of the options in our bug tracker, such as "code", "test data", "tester error" etc.
Senior QAs believe that details about root cause should be mentioned by the developers who fix the bug, not QA. I disagree because I believe that QA finding out root cause (even at high level) has the advantages mentioned below. Note that my "Contrived examples" are quite similar to issues which I have seen.
1 - It enables QA to learn more about the system or even business domain.
Contrived example: A search functionality in a web app was not working for one test data. For another test data, it was working. So, was the error in the search engine or something else ? From dev, I learned that indexing would simply fix the error. In the process, i learned about the system and how to trigger indexing.
2 - It improves QA's knowledge & understanding on how bugs can creep in when they/dev can miss some test cases. They can use this knowledge to come up with more robust test cases for other situations.
Contrived example: On a web page, after clicking one button, an api is called. In rare cases, the response from the api gets delayed and the side effect is that other UI elements get disabled. Those UI elements are not related to that api call and should not be disabled if the response is delayed. The dev told me that delayed response caused the issue. Next time, when I do UI testing, I will see if I should simulate delayed api responses or not.
I am not sure if these reasons are compelling enough to make it mandatory for QA to mention root cause details in bugs.
So, should a QA mention details for the root cause for a bug or not ? Please mention the reasons also.
For this spec:
Feature: Buy car
Scenario: Jeff buys a car
Given Jeff sees a car he want
And he has the cash
When he pays cash
Then Jeff should own the car
The above spec file is called buy_car.feature and is placed in /spec/features/
The steps (Given, When, Then) inside Scenario: Jeff buys a car will reference the ruby file spec/features/step_definitions/buy_car_steps.rb which will have content like this:
Given("Jeff sees a car he wants") do |car|
perform capybara action to display car, e.g. visit, click, etc.
end
When("he pays cash") do |pay|
perform payment actions (front or back end as desired)
end
And("he has the cash") do |cash_check|
perform code to check bank balance is sufficient
end
...
I think this is right for where stuff goes and how it is named but welcome review and any correction. I've always found the cucumber docs a little hard to get started with so wanted to help with another simple example for folks getting started.
Add a Regular Expression Extractor and select "Main sample and sub-sample". Now you will be able to extract data from next request that you are talking about.