Date post: | 15-Jul-2015 |
Category: |
Software |
Upload: | sachin-natu |
View: | 366 times |
Download: | 0 times |
Death of Inspection: Reincarnation of the Testing community
Sachin Natu @natusachin
Naresh Jain @nashjain
26YEARS 7000+CLIENTS 1M+ ROOMS 94COUNTRIES 95%+
ago we started
helping clients
manage their
revenue
later we’re still finding
the revenue opportunity
in every situation
around the world are
priced every single day
using IDeaS
on 6 continents have
hotels that now run on
IDeaS Revenue
Management
Systems
More than 95
percent of all
our clients are
still working
with us today.
About IDeaS
Inspection - is synonym for Human Checking!
Checking is the process of making
evaluations by applying
algorithmic decision rules to
specific observations of a product.
Human Checking Vs Machine
Checking
Testing is the process of
evaluating a product by learning
about it through exploration and
experimentation, which includes to
some degree: questioning, study,
modeling, observation, inference,
etc.
Testing encompasses Checking!
Testing Vs. Checking
Inspection
Requirement spec is ONLY source of TRUTH.
Knowledge of code/model is ignored/not given importance
Finding defect is feather in the cap of Tester - demotivating for
developer - war between dev and QA
Inspection
Source: https://z1703858.wordpress.com/2013/11/16/the-art-of-fencing/
UI automation always keeps playing a catch up game. Late
feedback to developers leads to more complications.
Inspection
Manual regression is still
bigger portion of
regression testing.
Manual
Checking 45%
End- to End UI Tests 40%
Integration Tests10%
Unit Tests5%
Inspection (2012)
As time to market keeps shrinking, testing effort is usually
the biggest bottleneck. Leading to a burn out on the
tester’s side.
Inspection
Overall efficiency of this process is very low. Defects are found late in
the process, which leads to rework and increased cost
Inspection
WAR is not helping - Let’s collaborate!
Need of innovation - Emphasis on Defect prevention than detection.
Quality is everyone’s responsibility.
Checking must be automated and efficiently automated
Manual
Checking
End- to End UI Tests 40%
Integration Tests10%
Unit Tests5% Unit Tests 70%
Domain Logic Acceptance Tests
10%
Integration Tests 9%
Workflow API
Tests 6%
End to End
Flow Tests
4%
UI
1%
Typical test strategies lead to an inverted testing pyramid
This is the need of the hour….Courtesy: Naresh Jain @AgileFAQs.com
The Test Pyramid
Reincarnated Tgyptian!
i. Keep tests
pinpointed
ii. Put them where
they originate
iii. Keep tests
leaner
Domain Logic Acceptance
Tests 10%
Integration Tests 9%
Workflow API
Tests 6%
End to End
Flow Tests
4%
UI
1%
Unit Tests 70%
Plan for no manual checking
Think of regression automation right from day 1
TDD BDD
Reincarnated Tgyptian!
Developers learn more
and more on domain.
Testers get more insight in
programming/ modelling
Both are learning and
widening their
boundaries resulting in
better Quality.
Other Impacts
References
http://www.satisfice.com/blog/archives/856
http://agilefaqs.com/