11 April 2016

Concluding day of GMI Training

Concluding day of GMI Training

I collected my feedback and bid farewell to all my colleagues who assured to be in touch forever. I collected my experience letter from AMIT and the two completion certificates on Testing and Quality Management. I am extremely grateful that I had a chance to get real industry exposure and learn a lot of new things, made new contacts. This is something i can cherish for a lifetime and awarded by top managements at GMI for exhibiting core value of Creativity.

08 April 2016

Quality Management At Sapient

Quality Management At Sapient
Sapient|Approach emphasizes on quality delivery being the responsibility of each team member. Our processes and tools are geared towards enabling each team member in ensuring quality of their respective deliverables.
The guiding principles of Sapient’s Quality Management approach are to “make quality a way of life” and to “catch defects as early as possible”. To this end, our QM approach includes industry best practices for Quality Planning, Quality Assurance, Quality Control and Quality Improvement, and covers the entire life cycle of a product/software.
Below is a representation of the focus areas of our Quality Management approach: 
Test Driven Development: Test Driven Development (TDD) is a technique whereby developers code unit tests first. The tests determine what system code needs to get written. Using this technique ensures that there is unit test coverage for each functionality that gets developed and that there are no system code changes unless there is a failing test case. This technique also enables us to develop functionality in incremental steps and refactor as we go along, always ensuring that the developed code is of good quality. This leads our teams to maintain an exhaustive suite of automated unit tests using the best practices tools available.

Continuous Delivery: The design principle behind Continuous Delivery (CD) is to that “every change is releasable”. Continuous Delivery is about having a deployment pipeline and a team that work towards ensuring that the software is releasable at any point of time. This technique enforces discipline within the software project team and ensures that the continuous integration and deployment infrastructure required is setup - including version control, automated builds, automated unit, functional, acceptance and regression testing, and builds packaging. Sapient has a dedicated Delivery Agility team that has expertise in the industry leading tools that enable us to setup a continuous delivery framework for a project team.

Automation: Automation is an integral part of our delivery approach and helps increase efficiency by automating repeatable tasks. Listed below are some of the candidates for automation:
·         Test Automation: The design principles built into our test automation framework are to “Support multitude of test cases without linearly increasing level of effort” and to “Make the framework keyword driven, extensible and modular”.  Test Automation using industry best practices and tools enables our teams to shorten testing times, ensure consistency, allow for extensibility and improve predictability.
·         Process Automation: Our teams always look for opportunities to automate repeatable components of project processes. Our teams have also built excel macro-based program dashboards that present a snapshot of project status on demand.

Full Life Cycle Quality Assurance: Each project team has dedicated Quality Assurance personnel embedded within, that ensure quality of deliverables throughout the lifecycle of the project. Test lead and QA engineers work in parallel with the developers, business analysts from the beginning of the project until final acceptance. Test lead is responsible for test strategy plan (including tool selection) and its execution. Testers are responsible for designing, executing and automating functional/integration/system tests.

These focus areas, along with quality gates and continuous improvement enabled by our iterative development approach ensure that quality is given prime consideration throughout the project lifecycle.


05 April 2016

UFT Settings


UFT Settings
Global Testing Options
Global testing options affect both how to work with tests and the general appearance of UFT. For example, choose not to display the Start Page when UFT starts, or set the timing-related settings used by UFT when running a test. The values set remain in effect for all tests and for subsequent testing sessions.
Set global testing options using the Options dialog box (Tools >> Options) or by inserting statements in the Expert View.
Individual Test Settings
Use the Test Settings dialog box to set testing options that affect how UFT works with a specific test. For example, instruct UFT to run a parameterized test for only certain lines in the data table. The individual testing options specified are saved when a test is saved.
Set Individual Test settings using the Settings dialog box (File > Settings )


Phases in Quick Test/UFT testing process
1.PREPARING TO RECORD
oBefore recording a test, confirm that application and Quick Test/UFT are set to match the needs of your test.
2.RECORDING A SESSION ON THE APPLICATION
oNavigate through the application or Web site, Quick Test/UFT graphically displays each step that is performed as a row in the Keyword View
3.ENHANCING THE TEST
oInserting checkpoints to search for a specific value of a page, object, or text string, which helps in determining whether application or site is functioning correctly.
oParameterize the code to check that application performs the same operations with multiple sets of data.
oAdding logic and conditional or loop statements to add sophisticated checks in the test.

Recording Modes
Normal Recording Mode
oRecording based on events performed on the objects in the User Interface.
oDefault recording mode, is it also known as context sensitive.
oRecognizes objects in application regardless of their location on the screen.
Analog Recording
oAnalog recording is used for applications in which the actual movement of the mouse needs to be recorded. E.g. Drawing a mouse signature or working with drawing applications that create images by dragging the mouse.
oThe track of the operations recorded are stored in an external data file.
oUFT adds to your test action or scripted component a single RunAnalog statement that calls the recorded analog file. You cannot edit analog recording steps from within UFT
oTypes of Analog Recording:
oRecord relative to a specified window
oRecord relative to the screen
Low Level Recording
oLow-Level Recording is used when the need is to record the exact location of the operation on your application screen
oAll the keyboard input and mouse clicks are recorded based on coordinates(X,Y)
Insight Recording Mode
oThis mode enables you to record on any control (object) displayed on your screen, whether or not UFT recognizes the object's technology.
oYou can switch to Insight recording in the middle of a recording session for specific steps.
oUFT recognizes controls based on their appearance, and not their native properties.

Running Test Script
•Run – Execute UFT Test Script
•RUN FROM : Run a selected part of your test. Enables you to check a specific section of your application or to confirm that a certain part of your test runs smoothly.
•RUN TO: You can instruct UFT to run from the beginning of the test or action (Expert View only)—or from the current location in the test or action—and to stop at a particular step.
•DEBUG FROM STEP: can begin debugging from a specific step in your test or action when editing a test or action.
•RUN CURRENT ACTION option to run a single action in your test.
Update Run Mode - Updates the test object description, Checkpoints properties, active screen images and values.
Maintenance Run Mode - UFT identifies discrepancies between the objects in the repository and those in your application and then offers a solution for updating your objects and steps in real time.

Analyzing Test Results
•When a run session ends, view the run session results in the Test Results window.
•The Test Results window contains a description of the steps performed during the run session. For a test that does not contain Data Table parameters, the Test Results window shows a single test iteration.
•If the test contains Data Table parameters, and the test settings are configured to run multiple iterations, the Test Results window displays details for each iteration of the test run.
•The results are grouped by the actions in the test.
•Filters can be used to filter down only failed, passed, warning result nodes.



30 March 2016

Quick Test Pro Vs UFT XX (11.50,51,52,53)

Quick Test Pro Vs UFT XX (11.50,51,52,53)

·         Licenses for QTP or ST will work for UFT, but they can restrict some features. It’s recommendable to upgrade to UFT Licenses to take advantage to the complete functionality provided by the tool.
·         If you just need API Testing, you can use HP Service Test Standalone, however this option it’s not available for GUI testing.
·         HP Unified Functional Testing offers new Add-ins for GUI testing as such as: QT and Flex.
·         HP Unified Functional Testing is not considered to be newer version of either Quickest Professional or Service Test.
·         Insight Recording for GUI Tests, it enables us to record control(object) displayed on screen, even if it UFT does not recognizes the object technology.
·         Removed menus from UFT: Insert, Automation , Debug Menus
·         Added Menus under UFT : Search , Design, Record, Run, ALM





Unified Functional Testing - Introduction
Unified Functional Testing = Quick Test Pro (QTP) + Service Test(ST)
Here Quick Test Professional (QTP) is a functional automation testing tool and Service Test (ST) is used for API testing(non GUI)
UFT 11.5 can support mobile testing as well ,using this feature we can test out multiple mobile devices as well in simulators.
HP Unified Functional Testing [UFT] is a new tool released in December of 2012
Supported Technology: Windows 2012, Firefox 22-24, Chrome 27-30, IE10, HTML5 enhancement, .NET Framework 4.5, Citrix 6.5, PeopleSoft 9.53, Flex SDK 4.6.
Features:
New look and feel for BPT test editing inside UFT
Create web service activities from Network Capture Data (PCAP file)
Have checkpoints for PDF, Txt ,word , HTML AND RTF files
HP UFT Insight


Key Elements in UFT Window
Active Screen: Provides a snapshot of your application as it appeared when you performed a certain step during the recording session
Data Table: Assists you in parameterizing your test. The Data Table contains the Global tab and a tab for each action
Debug Viewer: Assists you in debugging your document. The Debug Viewer pane contains the Watch, Variables, and Command tabs
Information: Displays a list of syntax errors found in your test and function library scripts
Missing Resources: Provides a list of the resources that are specified in your test but cannot be found, such as missing calls to actions, unmapped shared object repositories, and parameters that are connected to shared object repositories


UFT Licenses Types Type of QuickTest/UFT Licenses
1.Demo
2.Seat License
3.Concurrent License

Add In
•Install all add-ins over a single UFT installation
•Select which add-ins to use for a particular QuickTest session
•Built-in support: Standard windows
•Other core add-ins: Web ActiveX Visual Basic
•External Add-ins DotNet Delphi SAP MultiMedia Terminal Emulator Java Stingray Siebel Small Talk Oracle PeopleSoft ………………………..and many more


UFT-11.5x Basics Training

      Automation Concepts
      QTP vs UFT
      Overview of UFT, Licenses & Add-ins
      UFT Settings (high level only)
      Recording a Test
      Running & Analyzing a test
Why Testing Tools?



Automated Testing Life Cycle
Which Test Case to Automate?
  • Tests that need to be run for every build of the application (sanity check, regression test)
  • Tests that use multiple data values for the same actions (data driven tests)
  • Stress/load /Web-Service /Smoke Testing  test cases are good candidates for automation.
  • Tests requiring a great deal of precision ,complex in nature and consume huge manual effort.
  • Functionalities which are stable and live under production system.
  • Test cases through which are required from good ROI perspective.
  • Test cases which are mainly suitable from business user perspective.
  • More repetitive execution! Better candidate for automation.




22 March 2016

Introduction on Selenium Tool



Selenium is a free (open source) automated testing suite for web applications across different browsers and platforms. It is quite similar to HP Quick Test Pro (QTP) only that Selenium focuses on automating web-based applications.


Selenium is not just a single tool but a suite of software's, each catering to different testing needs of an organization. It has four components.


· Selenium Integrated Development Environment (IDE): selenium Integrated Development Environment (IDE) is the simplest framework in the Selenium suite and is the easiest one to learn. It is a Firefox plugin that you can install as easily as you can with other plugins.


· Selenium Remote Control (RC): Selenium RC was the flagship testing framework of the whole Selenium project for a long time. This is the first automated web testing tool that allowed users to use a programming language they prefer.


· WebDriver: It implements a more modern and stable approach in automating the browser's actions. WebDriver, unlike Selenium RC, does not rely on JavaScript for automation. It controls the browser by directly communicating to it.


· Selenium Grid: Selenium Grid is a tool used together with Selenium RC to run parallel tests across different machines and different browsers all at the same time. Parallel execution means running multiple tests at once.






Why do we need to automate?


§ To avoid human intervention


§ To make it fast and productive


§ To make it reusable or repeatable 


§ To make it reliable

18 March 2016

What is Automation Testing

  • Developing Scripts to Run the Test Cases Automatically and to Log the Results
  •  Software Test Automation is the process of automating the steps of manual test cases using an automation tool Or utility to shorten the testing life cycle with respect to time…
  •  When application undergoes regression, some of the steps might be missed out or skipped which can be avoided in Automation…
  •  Automation helps to avoid human errors and also expedite the testing process…
  •  To implement the Test Automation detailed planning and effort is required

Importance of Automation Testing
In today’s environment of reducing cycle times, test automation becomes an increasingly critical and strategic necessity. Especially in the new explosive pace of web-enabled deployment, if retaining satisfactory test coverage and reducing risk is required, then either more people have to be put on manual testing, or a greater level of test automation is required to keep the pace. After all, a reduction in project cycle times generally correlates to a reduction of time for test.
There are certain other aspects which make automation more helpful, some of them are listed below.
§ Increased speed of execution
§  Machine results are more replicable than human results
§  Parallel execution, Re-use of test cases etc are some additional   benefits.

Automation Fundamental Concepts

  • Automation life cycle is a subset of the entire test life cycle…
  •  Automation planning can be initiated in parallel to the test planning phase…
  •  Factors to be considered in automation planning,
  •             Stability of AUT (Application under test)
  •             No of regression cycles to be performed
  •             Compatibility of App platform with testing tools
  •             Cost benefit analysis (ROI)
  •             Availability of skilled resources