Mobile Banking Apps are increasing in reach and usage. MyBankTracker has written an informative brief about the Mobile Banking Apps of Wells Fargo, Chase, Citibank and Bank of America.
Click Here For Mobile Banking Apps Review
Tweet{ 0 comments }
From the monthly archives:
May 2010
I had the chance to go to the SV Selenium users meetup (#sfse) at Mozilla headquarters in Mt View,CA.The event had a fairly good attendance and there were two presentations by couple of guys from Mozilla (Stephen and Raymond) and Wade from LinkedIn.
The first presentation concentrated on how Mozilla has integrated their Selenium test suite into Hudson.It was interesting to see the journey from Selenium IDE to where they are today.In my experience it was a normal usecase while adapting to Selenium.The presentation was standard boiler plate but I would have liked to see some internal details.According to them the whole setup consist of Selenium Grid,multiple VM’s to run different browser and Hudson.However I couldn’t understand how the whole suite runs internally.They use python as the language for Selenium RC and had some interesting things about sharing common functionality etc.In all,it’s not unlike what I already knew but it was good to see validation of some of the approaches that I am taking in designing the Selenium framework
The second presentation was by Wade from LinkedIn and focused more on how the framework follows a page abstraction pattern to make the final testcases more readable and concise.The choice of language was Ruby and the framework took advantages of certain default functionality provided by Ruby(method_missing()) to allow the page abstraction.This was interesting but since I use Java,I am not sure if the same technique is so straightforward when using Java.The framework was inspired from Watir and an interesting adaptation for Selenium.
There were couple of side items brought up like what’s the best way to automatically generate XPath from the page as well as Http data generation.When I get an opportunity those two would be of something of interest to me to find out more.At the end got a chance to gripe about Selenium support for upload file and popup boxes.@hugs believes Selenium 2 will be much better,however I guess I will wait before trying my hands(Seen couple of feeds on twitter about not liking Selenium 2 and they had to revert back to Selenium 1).Also he’s going to meet with Dojo guys next month at some JS conference to see if they will have better support for Selenium in future.Would be nice.Testing AJAX is a nightmare with any tool not only Selenium.
Thanks to @saucelabs for the pizza before the presentation.Also got Alex from Saucelabs listen to my evaluation of Sauce labs.All in all good stuff,however I would like to see more technical details in the presentation.Link to the slides are here.There was video recording too.I will update with link as soon as it’s up.
Follow us on @infostretch
Tweet{ 0 comments }
After my last post on integrating Selenium RC tests with Hudson,I had few folks asking me on how I organized my test execution code with selenium RC tests.
If you are like me you probably started with running Selenium RC tests on your local machine and didn’t give much thought about integrating with Hudson,but when it was time,there was lot of files moving around and unnecessary cruft of code.
To run this sample,you will need ANT and Java on your machine
So here is a sample TestNG runner code which is ready for Hudson to consume and at the same time having a clean separation between Selenium RC tests and execution.This structure should make things easier when multiple team members are writing test cases allowing easier test code checkin to your version control system.So look at the attached zip file.Please find instructions on how to use this in the README folder.I have also included a sample Selenium RC project which the current TestRunner configuration points to.
This code is not intended to replace the Eclipse+TestNG plugin and it’s use in dev environment is highly recommended.But this code does the next step of getting your Selenium RC tests ready to be used by Hudson.For now the test runner is overtly simplistic and can only run a single TestNG configuration file,but feel free to extend this and make your own modifications to suit your needs.
When you are ready for Hudson to run your Selenium RC + TestNG tests,have your Hudson job execute the STunner/bin/seleniumtestrunner.xml and sit back and watch your tests run.
If your Hudson is on a Unix machine,look at my earlier post on Integrating Selenium Tests with Hudson CI
If you want how to convert your hudson cluster to Selenium Grid ,this post should help you.
Let me know if it doesn’t work for you or other issues that you face.
Follow us on @infostretch on twitter to get more updates on Selenium as well how we can help your organization get Selenium ready.We offer multiple Selenium solutions that fits every project size and needs.
Download the Selenium TestNG Runner from here
Important:The bundle doesn’t contain the selenium-server.jar as the size of the bundle increases.So the very first thing you will need to do is to download selenium server and copy it under ‘server’ directory.
Tweet{ 0 comments }
Most of the customers/companies always look for optimizing the process for better results, so they will give high priority to the experience expertise’s in their new venture because they can add value to S/W Testing. So one of the key factors for any success is adding Domain expertise’s to the Project/Product.
Domain expertise is important in software testing because the person who has domain knowledge can test the application better than others. The domain knowledge plays an important role in software testing as one of the software testing principle says “Testing is context driven” which means the testing performed for a Financial application is different than testing done for Insurance/heath care application.
When we test a particular product, we have two kinds of axis where Y axis denotes the technology and where as the X axis denotes the domain. Domain is common for all technologies. Domain experts can write the business driven scenarios to execute the actual business, whereas Technology experts will be able to write scenarios on the technology which makes their scope narrow.
Advantages of Domain knowledge:
- Reduces the Training time: A person can be productive quicker than a person that has zero domain/industry knowledge. So it adds value to project/product.
- Good idea on Functional flow (Work flow), the Business processes, and Business Rules: It will help in better way to understanding the product requirements.
- Good idea on UI features: It will help the person for improving the look & feel as well caught more bugs at initial stage itself on UI front.
- Good idea on Back end Processing: how effectively/ efficiently the data/code is handled
- Domain knowledge is also important to defect triage: Knowing how the application will likely be used and how it is expected to perform, will tell QA whether a given defect is trivial, significant, or critical.
- Terminology: Reporting in the language of the business, resulting in good rapport with the business team
{ 6 comments }
