Thursday, June 15, 2017

About Me

Technical
I have overall of 12yrs of exp which includes working with different domains like Server, Storage, cloud, mobile app, web app, Healthcare domains.
Started career with IBM (software labs, worked with Websphere, Rational, Business analytics grps), then worked with some startups and now with Dell(EMC).
Currently I am an Senior Automation Architect for of Hybrid cloud engineering group of EMC-India centre of excellence.
Evaluate the tools, analyze, do the POC, create Automation strategies, provide the estimations
We build the cloud.
Work with global teams, prepare test strategies, best practices.
We work in a fast pace, rapid releases; supporting multi site, multi tenant deployments in distrubuted environments which are highly scalable following scrum, CI/CD using Jenkins, bamboo, git.
I have developed Automated tool in similar lines of RFT and selenium on Eclipse. Nesses Scans for finding vulnerabilities.
Where in we have to write simple english [just like testcases], to test the functionality.
I have exposure in working to various frameworks, developed from scratch.
Atelast 6-7frameworks.
Exposure (working experience) to DevOps
Using CI/CD: Improve the qulaity of the build. reduce the manual efforts in testing.
Shift left model, Agile test pyramid
Release to release unit testing, Integration testing, BVT, sanity, fucntional testing, Regression testing.
Published several technical articles on RFT.
Feature contributing Author of Rational. Online trainer for RFT.
Certified cloud professional, from VCE: Certified from IBM on RFT, RPT, Solution designing.
Sun certified Java
As a responsible Subject Matter Expert, I have to be answerable in resolving questions arising from the development team, BAs, users and management
About Solution: Native Hybrid Cloud is a turnkey platform that provides the fastest path to digital transformation accelerating time to market and enhancing customer experiences.
Managerial
I have overall of 12yrs of exp which includes working with different domains like Server, Storage, cloud, mobile app, web app, Healthcare domains.
I have started career with IBM, worked with different grps like Rational, WebSphere, Business Analytics grps. Later moved to startups: worked as an Automation Architect for 6-7yrs.
Worked with several automation tools and languages. Developed several automation frameworks….Finally, I have developed an in house automation tool for startups.
Certifications, Articles, RedBooks.
Currently from past 3-4yrs took the QA Manager role and now handling 12members for Cloud Solution[NHC]. We build the cloud, PaaS
Work with senior leadership team.
·         Any organization I go, I check what is the best that I can give, what is the ROI,  that I am giving. Like I analyze historical data to build quality improvement initiatives and drive quality strategies across the network. Build a quality culture. [eg: Agile, CI CD, Pairing, Automation, Model Based Testing]
·         Estimate, prioritize, plan, and coordinate testing activities
·         Own the development of robust quality feedback loops into training, analytics, and process to drive continuous improvement.
·         Identify and analyze data to isolate issues, identify trends, develop solutions and prioritize opportunities for overall process improvements.
·         Create, maintain and disseminate project information to stakeholders and senior management.

Day to Day job:
Interact regularly with Global Stakeholders, Product Owner, Program managers, Dev Managers, Scrum Master & test team to understand the daily progress, status, impediments etc etc.
Outside grp: Lab-ops, SIT grp, Hardware grp(once per release)
Work in fast paced, rapid releases, multi-site heterogeneous environments. Make sure the Quarterly releases go smoother & clear technical challenges or any impediments if the team is facing.

Talk to PO, review the backlogs, check the PSI content for every release.
Get the E2E use cases at customer env.
Remove the impediments if the team is facing anything related to infrastructure or technically in Automation. Give the approvals where required.
Participate in PSI planning, Sprint Planning, Iteration Planning, Review meetings, Triage calls, Sprint of Sprint meetings.
Monitor all operations that affect quality
Appraise customers’ requirements and make sure they are satisfied

Regular 1:1 on the career goals, setting goals for the team.
We work in a fast pace, rapid releases;
Supporting multi site, multi tenant deployments in distrubuted environments which are highly scalable following scrum, CI/CD using Jenkins, bamboo, git.
Accomplishments:
·         CI/CD Implementation for build quality and improvise it.
·         70% Automation across all 3platforms. which reduced the regression efforts
·         Fail fast and Fix fast.  Gel between QA and Dev.
·         Updates from Tools, not from person, made this very dynamic, transperant and visible till Director. [Automation Dev Status, Test progress, Results sprint over sprint, Pie Chart for all these, shows the accurate information]
·         Conduct 360 Feedback to everyone from everyone.
·         Conduct C-SAT programs and get the reviews, drive the improvement actions


I have exposure in working to various frameworks, developed from scratch. At least  6-7framewok

Wednesday, June 14, 2017

Amazon

About yourselves:
Experience in setting up QA process. Automation Roadmaps, Framework Architecture…
People Management.

Round 1: Metrics, Test planning/strategy
Round 2: Framework/automation
Round 3: *Coding/Prob solving [maps, arrays, string, arraylist]
Round 4: *Hiring manager round – Best Fit, leadership principles. Delivered instances.
Round 5: Bar raiser round [hiring manager]

Test Plan:
1.       Introduction
2.       Objective
3.       Scope
4.       Test Strategy/Approach
a.       Automation
b.      Manual
c.       Regression
d.      API…etc levels of testing
5.       Features to be tested and not tested
6.       Entry Exit Criteria
7.       Schedule
8.       Tools
9.       Trainings
10.   Resources
11.   Risks/Assumptions
12.   Hardware
13.   Test Env
14.   Significantly Impacted Departments (SID)

Test Design techniques:
Black box Design techniques.
·         Equivalence partition technique [Saves time in testing and allows you to find more defects in less time. Divide the test data into partitions. Test each partition once.]
·         Boundary value analysis
·         State Transition technique [This technique is used when the system is defined in a  finite no:of
states]
·         Error Guessing
·         Cause effect Analysis
·         Use Case Testing
White Box Design techniques
·         Condition coverage – A major percentage of the outcomes of test conditions are exercised by this technique. Condition testing is a white box test design technique, wherein the test cases are designed in such a way that the condition outcomes are executed.
·         Decision coverage – Here the test design technique exercises the percentage of the outcome of the decisions and designed in such a way that decision outcomes are executed.
·         Statement coverage – This technique is involved in calculating the percentage of executable statements that are being exercised by the test suite.

Test Metrics:
Process Metrics: Metrics that pertain to process quality. Used to measure the efficiency and effectiveness of the process eg: waterfall/agile..etc
Product Metrics: Metrics that pertain to Product quality. Used to measure the quality, cost & product’s time to market.
Project Metrics: Metrics that pertain to project quality. Used to quantify defects, cost , tools, schedule, productivity and estimation of various project resources and deliverables

Different stages of test metrics: Analysis, Communicate, Evaluate, Report

Requirements Metrics:
Req coverage= no:of req covered/total no:of req * 100

Automation – Manual % Coverage
Code Coverage (for unit testing, integration testing)

Performance metrics
·         Webserver Performance Metrics [throughput, bandwidth req]
·         AppServer Performance Metrics [cpu hotspots, load distributions, worker threads, mem issues]
·         Application Performance Metrics
Eg: MVC model view control, put load on application and check which layer is taking more time for responding/execution, so that we can think of scaling]

Horizontally scalable
Deploy applications on 100 small machines and check application performance.

Checkins
How many checkins manual/automation?
If manual, why they are manual. Any automation issues?
How many checkins are successful and how many are failures.

Internal/external defect ratio:
Quality of defects that the testing team rasied.

Test Execution Metrics:
Every day, the trend has to be followed on this test execution, which is more important.
In CI execution, test executions should be successfully passed and we made a goal that no builds should be in RED in two consecutive days. So that everyone works for this goal and we have releasable builds.

Defect Metrics:
·         Defect Category [Security/Performance/Functional]
This ratio tells the QA Manger that where is the major defects found, so that he can concentrate more in the next phase in these areas/categories.

·         Defect Density (should be less)
                Total defects found/Total no:of lines
Or
                Total defects found/Total requirements
Lesser the density, more quality is maintained.

·         Defect Detection Percentage:  [DDP should be great]
(should be more, greater the DDP, it tells the efficiency & reliability of testing process)

      No:of Defects found during testing/automation
= -------------------------------------------------------------------------        *100
    ( total no:of defects found in the testing phase + escaped defects + customer defects )


·         Defect Removal Efficiency: (greater the %, greater is the quality)
Generally DRE is calculated during the version release.
Total Defects resolved by dev/ total defects found * 100
Greater the count, great is the efficiency and accuracy.

·         Defects Leakage: (should be less)
Defects Slipped/total defects *100

·         Defect Severity Index (should lower, from phase to phase): An index representing the average of the severity of the defects. Provides a direct measurement of the quality of the product—specifically, reliability, fault tolerance and stability. Two measures are required to compute the defect severity index. A number is assigned against each severity level: 4 (Critical), 3 (Serious), 2 (Medium), 1 (Low). Multiply each remark by its severity level number and add the totals; divide this by the total number of defects to determine the defect severity index.

·         Defect containment is nothing but checking not to propagate defects from 1 phase 2 another phase

·         Mean time to Detect MTTD = No:of issues detected /execution time
·         Mean time to Resolve MTTR = No:of issues fixed /total coding time
This gives the QA manager details of how efficient the testers/developers are.



14 Leadership Principles examples.

  1. Customer Obsession
  2. Ownership
  3. Invent&Simplify
  4. Are Right a lot
  5. Learn & be curious
  6. Hire and develop the best
  7. Insist on high standards
  8. Think Big
  9. Bias for Action
  10. Frugality
  11. Earn Trust
  12. Dive Deep
  13. Have Backbone, disagree and commit
  14. Deliver results



Invent the economical approaches and simplify the things.
Automation Navigate to Page example.
For short term goals, I can’t sacrifice the long term goals.

Dive Deep: Due to my interest in coding, I keep taking the technical challenges.
Support the developers when required.
Eg: Google Collection Framework
Eg: Tell about the design change. Backingup of 500GB disks everytime no matter whether the content is there or not is tedious. Instead backup the files which will reduce the time and cost.

Learn new technologies, take trainings in management skills. Recent trainings on learn to unlearn”

Frugality: Economical. Make things reusable. Do not re-invent the wheel.
Navigate to Page.

Trust & Ownership: There was a merge with Dell, and people started looking out. Architects, managers, team...etc etc…
There were some layoffs as well. Existing team was very panic.
I took complete team to a room after the news and then gave them the clarity and shown them the future roadmap.
For the release, I asked all the team to put all action items on a board and what is that we can chew at this moment and then took the plan to release it.

Later talked to the director on the dates and the director was helpful in this regards, as she knows the situation and she appreciated for the effort I have kept.