TanRid

Continuous Integration (CI) is a software development practice, which insures that changes to a project’s code base are built, tested, reported on, and rapidly made available to all parties after they are introduced. This framework frees developers from having to constantly create new builds for the Test and QA groups. Each subsequent build is established and promoted, then downloaded automatically for testing.

The basic premise of CI is pretty straightforward – your team needs a reliable method to create a build of the software under development, that happens on a continual basis. Why so? Well, if its not already obvious, this enables a team to receive frequent feedback about software quality earlier in the development cycle, thus helping to avoid potential downstream issues and defects. Also, if your team size is greater than one, integrating each developers work in a regular, repeatable fashion (perhaps hourly) will help significantly in highlighting any code integration issues.

Appium is an open-source test automation framework for testing native and hybrid apps and mobile web apps. It drives iOS and Android apps using the WebDriver protocol.

A huge advantage Appium has over other mobile test automation tools is tests can be written in any language that has a Selenium client library. This means you don't have to learn a special language, just develop tests in the language you are familiar with so you can be efficient. And, since Appium tests run across both iOS and Android, you can run your tests across the devices that your users are likely to have.

There are many test automation frameworks to choose.

Many popular are Selenium,PhantomJs,CasperJs. A headless browser is a web browser without a graphical user interface. Headless browsers provide automated control of a web page in an environment similar to popular web browsers, but are executed via a command line interface or using network communication

REST Assured is a popular framework to do test automation and REST API Testing This is one of the framework choices of TanRid

API testing is in many respects like testing software at the user-interface level, only instead of testing by means of standard user inputs and outputs, you use software to send calls to the API, get output, and log the system’s response. Depending on the testing environment, you may use a suite of prepared test applications, but very often, you will wind up writing code specifically to test the API. Regardless of the actual testing conditions, it is important to know what API test code should do.

Needless to say, API test code should send a specific call to the API, then output and log the expected and actual results. It should also log timing and any other relevant metrics (unless they are more easily captured by system debugging tools), along with line of test code that was running when an API error occurred. If the test code sets a memory buffer that is larger than that required by the API, you can then look at the contents of the buffer for improper overwriting on the part of the API. The test code should capture all API outputs produced during the course of the test, using variable which are initially set to distinctive values that would not be produced by the API itself; this makes it easier to recognize the API outputs as you look at the variable values.

Cross-browser testing is the process of reviewing and comparing website functionality and styles across multiple browser platforms, operating systems, and mobile devices to uncover any potential discrepancies. We all have a preferred browser that we use daily, so it can be easy to forget what the rest of the population is using to access a website. Whether you’re a developer, designer, or quality control inspector, you have to consider the countless methods end-users can utilize to interact with your website.

One of the main aspects of cross-browser testing to keep in mind is that CSS styles render differently across browsers/browser versions, especially in terms of what is supported and what is not. Older versions of Internet Explorer are generally the most affected by unsupported CSS elements and newer HTML tags.