12
QA AND A UTOMATION [email protected]

Imaginea qa&automation

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Imaginea qa&automation

QA AND AUTOMATION

[email protected]

Page 2: Imaginea qa&automation

CO

NF

IDE

NT

IAL and P

RIV

AT

E. D

o not forward or share w

ithout written

consent from Im

aginea. Copyright ©

2011, Imaginea, Inc.

We test and own whole products, the experience, the features, the release–we are product engineers.

Our Differentiator

Page 3: Imaginea qa&automation

Acceleration with Imaginea

• Blend of home-grown, open source, and commercial automation tools

• Engineers with wide array of tools, automation skillsets and best practices

• Proven expertise in choosing what to automate, tools and frameworks with a consistent focus on maintaining the quality of test cases

• Test suites & frameworks for repeatability, coverage, efficiency

• Integrated test solutions suitable for both startups and established shops

• Rich history in automating product testing and web vulnerability testing since web app server days, we hire software development engineers in test

Page 4: Imaginea qa&automation

Imaginea Test Engineering Process

Product explanation and Test strategy definition

1 Vision & Test Planning, Processes, Tools, Performance Tests, Platform Certification, Tech Pubs

Complete test plan, architecture, test cases, use cases, scenario matrix, test bed and infrastructure definition

Functional QA 2 Feature understandings, use case identification, Functional Testing (Manual, Automated, Regression),

Complete test execution, build wise reports, adhoc, system,integration, blackbox and white box tests

Automation and Regression

3 Automation scenario identification, framework development, unit and function test automation, nightly builds and reports

Automation estimates, Test development and scripts, regressions , RoI and test cycle time reduction

Performance and Security testing

4 Benchmark identification, Load parameter definitions, scalability and peak performance definitions, Security parameter definition

Stress, Load and reliability tests, injection attacks, DDOS, sniff tests

Platform certification

5 Platform matrix identification, Interop Lab setup, Automated platform test suites

Interop testing, Platform certifications, Browser compatibilities, Multi Platform testing

Go To Market readiness Program

6 Use case driven testing, Fresh test infrastructure close to customer environment, Product Management and Mktg testing, Beta feedback

Test Suites, Harness, Go-To-Market Testing, Alpha, Beta Testing, Product Docs, GA

Page 5: Imaginea qa&automation

CO

NF

IDE

NT

IAL and P

RIV

AT

E. D

o not forward or share w

ithout written

consent from Im

aginea. Copyright ©

2011, Imaginea, Inc.

Identify the Key Architect / Technical Lead We invest upfront in identifying the product owner and single point of contact. Such a person comes with the right mix of technology and maturity, and is the key to success of the engagement.

Assemble the Right Project Team Based on [1], the owner studies requirements and mode of engagement with client, and assembles a team with right mix of skills, attitude, and seniority for the assignment.

Implement and Review Project We always work with a roadmap to prioritize and pace our work. We work in an Agile environment with high visibility for all stakeholders. Styles will differ between fixed bid and time/material projects.

Onboarding Process Aimed To Please

1

2

3

Page 6: Imaginea qa&automation

CO

NF

IDE

NT

IAL and P

RIV

AT

E. D

o not forward or share w

ithout written

consent from Im

aginea. Copyright ©

2011, Imaginea, Inc.

Typical Team Structure

Technical QA

Manager

Principal QA

Senior QA Senior QA

QA Engineer QA Engineer

QA Management, DRI,

Response Times, NPS tracking,

Billing

Writing test cases, PoCs,

Technical reports, team

upgrades, training

Daily tickets, closures,

development, communicating

with Client engineers

Daily tickets, implementations,

resolutions, fixes QA Engineer

Page 7: Imaginea qa&automation

Automation Challenges

• Automation is a development effort, not ‘record-n-playback’

• And there are challenges:

• Systems: Frequent changes and enhancements

• Teams: Unrealistic expectations, wrong tools

• Tools: Reuse/Adapting for new platform requirements

• Challenge: Communication Gaps When Moving from Manual to Automation is one of the prime reasons for automation failures.

Page 8: Imaginea qa&automation

Case: BrighTest for agile applications

• Built at Imaginea for product engineering efforts • Java-based tool built on Selenium–to keep the

test suite up with the changes of an evolving code base

• Rich test format with extensive test details. Use of XLS cuts down on the verbosity of ‘Selenese’ without compromising on the ease of recording or playback.

• Have callbacks to scripts in other languages like Java. Python leverages LiveConnect.

• Add commands with immediate integration, no browser restart needed.

• Externalize key properties and templatize frequently used commands to provide DSL-like features.

Page 9: Imaginea qa&automation

Case: Bot-Bot, automating on Android

• Selenium-like keyword-driven automation framework for native Android applications

• Test-cases defined in csv format converted to Java files and then executed using TestNG execution framework, Selenium Native Driver and Ant

• Server: Records user actions through Recorder and allows users to export their test-cases

• Recorder: Tracks user actions at the android app side and then send them to the Server

• Runner: Allows user to run their recorded test-cases on the actual android application as a suite

• Generates HTML reports at end of test execution

Page 10: Imaginea qa&automation

Case: JDBC Compliance Test Suite

• Global search platform provider wanted its drivers to be certified • Imaginea test suite helped the customer deliver robust, reliable SQL driver

conforming to the JDBC 4.0 specifications • JDBC test suite covering 17 chapters with 1800 test cases • Transaction compliance of the driver against JTA and XA contracts • Leveraged our application server experience

Page 11: Imaginea qa&automation

CO

NF

IDE

NT

IAL and P

RIV

AT

E. D

o not forward or share w

ithout written

consent from Im

aginea. Copyright ©

2011, Imaginea, Inc.

Working across the globe has its advantages, if overlapping hours are used effectively and clear communication is established. Our teams in India share a 2 to 3 hours overlap – depending on the working hours. During Go Live, overlap can be up to 8 hours.

Overlapping Hours: Making the most of “Follow The Sun”

Plan, Work and Stage.

Reviews, Tests, Reports Our AM

Daily

Offshore

Scrum

Your AM

Wednesday Thursday

Imaginea

Updates

9:00 IST India 08:30 EST

18:00 IST India

Twice a Month Project

Management Sync Up

Our PM

12:30 EST

22:00 IST India

Daily

Standup

Meetings

Close

Of Day

Updates

9:00 IST India

Client

Updates

Extended offshore day

during release time

Page 12: Imaginea qa&automation

EVENTUALLY, BETTER PEOPLE LEAD TO BETTER SOFTWARE.

[email protected]