published by Anonymous on December 27, 2016 - 15:16
Continuous integration approach is very helpful for Agile projects. Nearly everyone has been using or at least considering to use it for Unit testing, isn't it right? But automated visual/CSS testing on Jenkins or other CI tool seems to be much less popular. Why it is so? First of all, you need to have a visual testing solution which is well-compatible with your CI tool of choice. Unfortunately, integrating them is typically not a simple task.
Our team has successfully implemented automated CSS testing on our Jenkins server with the help of Screenster, our QA automation tool which does not require coding and is free to try - on premise and in the cloud. It allows QA automation engineers to:
The primary purpose to calibrate a set automation tools is to perform data driven automated testing applications on Android.
Start with setting up the environment using following tools: Install JDK, Eclipse 3.4 (Ganymede) or greater and Android Development Tools plug-in.
Next install Android Emulator from the eclipse window menu select Android SDK and AVD Manager.
After the environment was setup successfully, I started with creating a very simple temperature convertor application to better understand the architecture & UI interfaces of the Android SDK.
We all knows that API is an interface that is used by the programmers to make communication from your system's application to other applications/third party servers. The developers connect to the APIs to make requests and get responses from other applications as required. And there are various challenges that software testers face in testing API.
To perform API testing you must be aware about the challenges and how to overcome them and you must learn the best practices to perform API testing perfectly.
I am sharing here top 4 challenges about API testing :
Commentators have provided multiple definitions of SOA. The OASIS group and the Open Group have both created formal definitions. OASIS defines SOA as the following:A paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations.
Documentation - Testing the quality of the documentation, e.g. user guide or installation guide.
One of the key factors demonstrating the maturity of the testing tool is the documentation.
Documentation is most crucial on to kick-start with the tool and later when facing complicated scenarios.
Most important is reading about list of features and capabilities, with examples. Today some of the tool documentaries are even include video tutorials.
Hi My expertise is in Web testing along with writing test cases, Test case Execution.
I have good Exposure of testing tools like JIRA,QC and hands on experience in Database and Mainframe testing and have experience working in agile model.
Recent comments