Selenium IDE is the a Firefox plugin that does record-and-playback of interactions with the browser. Use this to either script simple scripts, or to speed up creation of Selenium RC or Selenium Webdriver scripts.
//Data Driven Test Framework using Selenium and TestNG //This Test performs search for the movie and looks for the attributes on the result page //Data is read from the Excel SS - imdb_data1.xls package script;
@Test (dataProvider = "DP1") public void testDataProviderExample(String movieTitle, String directorName, String moviePlot, String actorName) throws Exception { //enter the movie title selenium.type("q", movieTitle); //they keep switching the go button to keep the bots away if (selenium.isElementPresent("nb15go_image")) selenium.click("nb15go_image"); else selenium.click("xpath=/descendant::button[@type='submit']"); selenium.waitForPageToLoad("30000");
//click on the movie title in the search result page selenium.click("xpath=/descendant::a[text()='"+movieTitle+"']"); selenium.waitForPageToLoad("30000"); //verify director name is present in the movie details page verifyTrue(selenium.isTextPresent(directorName)); //verify movie plot is present in the movie details page verifyTrue(selenium.isTextPresent(moviePlot)); //verify movie actor name is present in the movie details page verifyTrue(selenium.isTextPresent(actorName)); }
@AfterClass public void tearDown(){ selenium.close(); selenium.stop(); }
Playing around with idea to develop a testing tool-kit for Android. With so many applications being built, there is a dire need to shorten the time to market. That is the main reason, most of the applications available in the market either crash or do not meet user expectation. It is apparent that the quality is veiong sacrificed in order to mee the deadlines. To ensure that the Android apps are delivered with quality and also in time, there is a need for a testing framework that can check on the quality of apps on certain standard parameters as below:
1. Installation testing:
Tester’s need to focus on installation & uninstallation of the app. User will install the app through Market place, but since the app is not in market place testers can use the app installer from marketplace for installation tests.
2. Requirement (Functionality) Testing:
Test for the application functionality according to designed test cases.
3. Widget testing:
Test the widget by adding widget, using widget as per functionality i.e. music widget should play music, deleting widget.
4. Phone Interrupt testing:
Test the application behavior on phone call, SMS & other notifications.
5. Stress testing (monkey test):
There is a command in android where it generates series of events at different frequencies.
Make sure your app passes this monkey test
6. UI testing:
Testing for UI can be done to verify that the app meets standard guidelines.
Developers do the unit testing on the emulators. Testers need to test on actual environment i.e. devices. There are multiple devices of different resolutions & having various OS i.e. Android 1.5, 1.6. 2.1 & 2.2. We need to check for compatibility on maximum devices.
@echo off echo Starting Selenium RC server. . . Hit Control+C to stop. pause cd C:\selenium-remote-control-1.0.3\selenium-server-1.0.3 java -jar selenium-server.jar
Note: Param 1,2,3 - For launching RC Param 4 - RC Mode Param 5 - Browser Param 6 - Base URL of Test Suite Param 7 - Test Suite file with full path Param 8 - Name of the Report html file
Important: Before running bat file, run Test Suite manually to ensure that it runs and also check the file paths.
function formatCommands(commands) { var result = ''; var sep = SEPARATORS[options['separator']]; for (var i = 0; i < commands.length; i++) { var command = commands[i]; if (command.type == 'command') { result += command.command + sep + command.target + sep + command.value + "\n"; } } return result; }
function parse(testCase, source) { var doc = source; var commands = []; var sep = SEPARATORS[options['separator']]; while (doc.length > 0) { var line = /(.*)(\r\n|[\r\n])?/.exec(doc); var array = line[1].split(sep); if (array.length >= 3) { var command = new Command(); command.command = array[0]; command.target = array[1]; command.value = array[2]; commands.push(command); } doc = doc.substr(line[0].length); } testCase.setCommands(commands); }
function format(testCase, name) { return formatCommands(testCase.commands); }
JUnit 4 and TestNG are both very popular unit test framework in Java. Both frameworks look very similar in functionality. Which one is better? Which unit test framework should i use in Java project?
Regular Expression Is used by adding the regexp prefix to your pattern: regexp:pattern
Selenium uses the JavaScript implementation of regular expressions (Perl-based):
·any character matches its literal representation: abc will match abc
·[ starts a class, which is any number of characters specified in the class
o[a-z] will match any number of lowercase alphabetical characters without spaces: hello, pizza, world
o[A-Z] does the same with uppercase characters
o[a-zA-Z] will do the same with either uppercase of lowercase characters
o[abc] will match either a, b or c
o[0-9] will match numeric characters
o^ negates the character class is just after [: [^a-z] will match all but lowercase alphabetic characters
o\d, \w and \s are shortcuts to match respectively digits, word characters (letters, digits and underscores) and spaces
o\D, \W and \S are the negations of the previous shortcuts
·. matches any single characters excepts line breaks \r and \n
·^ matches the start of the string the pattern is applied to: ^. matches a in abcdef
·$ is like ^ but for the end of the string: .$ matches f in abcdef
·| is equivalent to a logical OR: abc|def|xyz matches abc, def or xyz
·| has the lowest priority so abc(def|xyz) will match either abcdef or abcxyz
·? makes the last character of the match optional: abc? matches ab or abc
·? works in a greedy way: it will include the last character if possible
·repeats the preceding item at least zero or more times: ".*" matches "def" and "ghi" in abc "def" "ghi" jkl
·*? is the lazy star: matches only "def" in the previous example
·+ matches the previous item at least once or more times.
·{n} will match the previous item exactly n times: a{3} will match aaa
o{n,m} will match the previous item between n and m times with m >= n and is greedy so it will try to match m items first: a{2,4} will match aaaa, aaa and aa
o{n,m}? is the same but in a lazy way: will start by matching at least n times and increase the number of matches to m
o{n,} will match the previous item at least n times
·Common regexps:
o\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3} matches an ip adress but will also match 999.999.999.999.
o(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?) will match a real ip adress. Can be shortened to: (?:\d{1,3}\.){3}\d{1,3}
o[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4} matches an email adress
You go to the menu Option >> Option >> General Tab >> Second field on the form, change the value to the miliseconds of default time-out.
In RC: open("http://www.google.com"); // Default timeout being used setTimeout(new timeout val); open("http://www.google.com"); // Now Specified timeout being used
For a simple modal window there is nothing out of ordinary that needs to be done in Selenium. I am sharing sample code for automating modal window as below:
Selenium 1 has been there for long time and most of the people I know working in this tool have been working on Selenium 1. The Selenium 2 has also been in news since last one year, more so after knowing it will be merging the two projects Webdriver (by Google) and Selenium 1. This seems like a great news as this overcomes the major drawback on Seleniuim 1, the "same origin" problem (rather than running as a Javascript application within the browser), WebDriver controls the browser itself. This means that it can take advantage of any facilities offered by the native platform.
As I have been observing the Selenium 2 project very closely, I noticed that they are not following the "bing bang" integration approach, i.e. the features of Selenium 2 (which have its origin into Webdriver) started to creep into the Selenium RC server over the last one year.
Now Selenium 2 is officially out there, still not very stable and also the lack of documentation is a challenge. However whatever I got to test using the Selenium 2 has been very encouraging, gives you a lot of control and the "same origin" problem is completely avoided.
Now the big question, Selenium 1 or 2?
There in no Selenium IDE or GRID for Selenium 2 yet and that could be the deciding factor for many.
If you are hands-on programmer (esp. java) then you can directly start with Selenium 2. Otherwise, I will recommend that you start with IDE, record and run the formatted code in RC (Selenium 1) and then slowly migrate to Selenium 2.
Another deciding factor, since Selenium 2, even though released officially, it is still a beta release and it might be risky affair to run your client's test scripts on a beta release. So, definitely practice and learn Selenium 2, however wait up for it's official "full-blown" release at a later date.
Also if you need to use GRID then you need to stick to Selenium 1... at least for the time being.
Programming languages are supported through Selenium Remote Control "drivers." These are libraries made for each language that expose commands from the Selenium API natively in the form of methods/functions.
