Installing, Configuring and Executing jobs With Jenkins – Part 2 (Creating jobs and Executing )
Jenkins is an application that monitors executions of repeated jobs, such as building a software project or executing automation scripts.
This is the Part 2 of the Jenkins guide. You can visit the first part from here.
Installing, Configuring and Executing jobs With Jenkins – Part 1 (Installing and Configuring)
Jenkins is an application that monitors executions of repeated jobs, such as building a software project or executing automation scripts. Among those things, current Jenkins focuses on the following two jobs:
- Building/testing software projects continuously
- Monitoring executions of externally-run jobs
This article will guide you how to install and configure Jenkins in an project environment.
Improving code quality with FindBugs – Part2 (Fixing bugs found by FindBugs)
In the first part of the tutorial we installed and configured FindBugs plugin in the Eclipse IDE. Go to the Part 1 of the tutorial from Improving code quality with FindBugs – Part1.
In this post we will look in to resolving the bugs found by FindBugs plugin.
Improving code quality with FindBugs – Part1 (Installing and configuring FindBugs in Eclipse)
FindBugs is a static analysis tool that examines your class or JAR files looking for potential problems by matching your bytecodes against a list of bug patterns. With static analysis tools, you can analyze software without actually running the program.
Findbugs provides early feedback about potential errors in the code. This helps the developer to access these problems early in the development phase.
Start using Android UIAutomator viewer tool in ADB
The uiautomatorviewer tool provides a convenient GUI to scan and analyze the UI components currently displayed on an Android device. You can use this tool to inspect the layout hierarchy and view the properties of UI components that are visible on the foreground of the device. This information lets you create more fine-grained tests using UI Automator, for example by creating a UI selector that matches a specific visible property.
Start using IOS UIAutomation tool in Xcode
You can use the Automation instrument to automate user interface tests in your iOS app through test scripts that you write. These scripts run outside of your app and simulate user interaction by calling the UI Automation API, a JavaScript programming interface that specifies actions to be performed in your app as it runs in the simulator or on a connected device. Your test scripts return log information to the host computer about the actions performed. You can even integrate the Automation instrument with other instruments to perform sophisticated tests such as tracking down memory leaks and isolating causes of performance problems
Modify the bash_profile in MAC for noobs
Are you stuck with a Mac computer and does not know a lot of unix commands and does not know how to set the path variables? OK this guide for youThis article will guide you on modifying the bash_profile in the Mac machines.
Troubleshooting – IOS web application automation with Safari
Automating web applications with Safari in ios devices needs several configurations. Appium uses an external application called Safari Launcher to launch the safari app in the real device. For that the app should be built and installed with the xcode command line tools under the hood from appium.
Troubleshooting – Android hybrid application automation in Android
Requirements:
To automate the android hybrid apps following requirements should be met.
- Device with Android 4.4+
- Android SDK 17, 18, 19
Troubleshooting – Appium web application automation in Android
Pre-requisites:
- Make sure Chrome (an app with the package com.android.chrome) is installed on your device or emulator. Getting Chrome for the x86 version of the emulator is not currently possible without building Chromium, so you may want to run an ARM emulator and then copy a Chrome APK from a real device to get Chrome on an emulator.
- If downloaded from NPM, or running from the .app, nothing needs to be done. If running from source, the reset script will download ChromeDriver and put it in build. A particular version can be specified by passing the –chromedriver-version option (e.g., ./reset.sh –android –chromedriver-version 2.8), otherwise the most recent one will be retrieved.