Test management for agile and SDLC projects... everything is achievable using one single solution. Design and run test during your iteration, capitalize for your projects

1. Create . Trust

2. XStudio supports both agile and
more usual SDLC

3. • Structuring your delivery ( agile exemple)
• Using KPI to monitor your progress and ensuring you
deliver with the right quality
• Testing Practices
– On-the-spot testing
– Sanned unit test ( and others …)
– Exploratory testing
• Smart campaign managment
– Residual campaigns
– Merge Campaigns
• And more

4. STRUCTURING YOUR SUT,
REQUIREMENTS, SPECIFICATIONS,
TESTS…

5. SUT
Requirements
SpécificationsTests
Campaign/sessions

6. • All SUT that are under development
Factory ( Future Release and new systems)
• Released and patches
Production (Currently in use)
• SUT that will be decommissioned
Retirement (under support, no more dev)
• For History and compliance only
Archive ( no support, no maintenance)
SUT
(Products,
MVP, Release,
Patchs) Move
Move
Move

7. •Need to be challenged, estimated , prioritized
Triage (new needs and ideas)
•Need to be allocated to application and sprint
Backlog
•In spec/dev/test
In development
•In use
Implemented
•No longer delivered in supported release
Retired
•Never implemented
Rejected
Requirements
(Themes,
EPICs, Users
Stories,
Constraints)
Move
Move
Move
Move
Move

8. In basket
•Collaboratively
understand the
need
•Estimate added-
value
•Collect in Theme
•Or reject
Backlog
•Associate to one
or more SUT
•Prioritize and
estimate
complexity
In dev
•Create necessary
specifications
•Associate to Dev
Sprint
•Dev and tests
work
Implemented
•Verify and
validate
•Verify test
coverage and
quality
Moving
requirements
from triage to
implementatio
n
Product
Owners
Product
Owners
+
tech lead
Product
Owners
+
Business
Analysts
+
Dev teams
Product
Owners
+
Business
Analysts
+
testers

9. •Business Process
•UI mockups
•Logic
•Data Flows and Structures
•Interface
Functional related
•Performance
•Usability
•Robustness and scalability
Quality attributes
•Security
•DevOps
•Compliance
Policies
•Tools
•Packaging
•Rules
•Infrastructure
Architectures
Specifications
Many common
Specifications
amongst SUTs
Just enough specification to start dev in a
sprint

10. MONITORING PROGRESS ,
COMPLETENESS AND QUALITY

11. Monitoring Projects with Key
Performance Indicators (KPI)
• XStudio Provides 4 main KPI
– Coverage by Requirements
– Coverage by Specifications
– Coverage by tests
– Quality
• Those are available for any SUT or group of SUTS
– You can drill down by
• Requirements (or group of it)
• Specifications ( or group of it)

12. HOW DOES THIS HELP ME WITH
MONITORING MY PROGRESS ?
… and
when can I be confident to release the solution ?
does this release cover what was expected ?
Will it be maintainable ?

13. Managing progress … and quality
• Initial release
• 14 weeks
• 2 weeks sprints
• Sprint 0 to plan
• Sprint Z to stabilize
• 5 Realization sprints
It sounds that this project is progressing correctly …
But are we doing all right ?

14. Know what you want to deliver
Know your constraints
Test as you go
Check your quality all along the
project
Coverage by Requirement Coverage by Specification
Specifiy just enough before each
realization sprint
Coverage by Tests Quality Progress by Tests

15. Measure your progress against common patterns
• At any time you can measure
your projects
• Set your standards progress
coverage and quality ratios
• Manage your project risk
against these patterns
• Decide if or when your SUT is
ready for release using
tangible KPI
• If not then analyze what you
should scope out
Common patterns and target quality

16. And don’t forget to Invest for the
future for your quality

17. AGILE AND EFFICIENT TEST
CONSTRUCTION

18. On-the spot testing
Create your
manual test
Try it on the
spot
• Untilit
covers your
need
Capitalize your
test and test
cases for others
• Use it in as many
campaigns as you
need
Decide if you
need to
automate it
•Automat
eit
This is what we call
the « playground »
Benefit: test your test
from the start using an
iterative approach and
during development
iterations and sprints

19. Develop and
use you unit
test
Scan and
import them
into XStudio
• automatically
Capitalize your
tests and test
cases for others
• Use it in as many
campaign as you
need
Manage your
regression
compaigns • Schedule it
Easy and fast
No specific
configuration
Scanned existing unit test
Benefit: You can map
all of your exiting test
script in Xstudio . No
need to define theml all

20. Exploratory testing
Test a specific
set of
functionnalities
Take notes and
create defects as
you go
• Use PDNL
Translate ad’hoc
test into scripted
tests
• Automatically
Review your test
and parametize
them
• Expand your
test coverage
Extremely efficient when testing
a delivery following a Sprint
Benefit: do the test and
automatically create the
the test from your results
(Avoid scripting and defining
procedure upfront)

21. CONTINUOUS TESTING

22. Continuous testing
You carry on trying 200 tests throughout he quality
cycles … very costly with manual testing
Initial
campaign
( 200 tests
And 1000
test cases)
Session 1 Session 2 Session 3 Session 4 Session 5
Benefit: ensure quality is
increasing and detect
regression sooner

23. Residual campaign
C1
Initial
campaign
(2000 tests)
C1 -Session 1 C2-Session 1 C3- Session 1 C4 -Session 1 C1 -Session 2
C2
Residual
campaign
(1500
tests)
C3
Residual
campaign
(100
0tests)
C4
Residual
campaign
(600
tests)
Benefit: Dramatically
reduce time spent on
testing what it knows to
work

24. Merged campaign
You testing effort and focus on those module
introducing the most risks
C1
Focused
campaign
On module
A
(100 tests)
Session 1
C2
Campaign
on Module B
(50 tests)
C3
Campaign
on Module C
(150 tests)
Session 2
C1 + C2 + C3
Campaign
On full
system
(300 tests)
Session 2
Merged
Benefit: focused testing
during sprint or per team
and then ensure fast
stabilization

25. Smart campaigns
Sprint 1
Campaign
(20 tests)
Regression
Campaign
on Sprint
1+2+3
(59 tests)Merge
d
Sprint 2
Campaign
(17 tests)
Sprint 3
Campaign
(22 tests)
Sprint 4
Campaign
(15 tests)
Sprint 5
Campaign
(15 tests)
Final QA
Campaign
on Release
(89 tests)
Merged
Benefit: mix all prior
benefits

26. Building campaigns
•Select all linked tests of one or more SUTFull regression testing of a
product
•Select tests linked to a Requirement folderFocus testing on a
module/component
•Merge Smaller Campaign
Regression testing campaign
•Manually select some tests for each concerned SUT
Smoke testing
•Exploratory testing
UAT
•Select interface ( e.g. SOAPUI) and orchestrate
dependenciesEnd-to-end Testing
•Distributed on a pool of XAgent
Performance / robustness testing
•Merge Modules focused campaign + Interface testing
System testing
Most Campaign can be deisigned in less than 5 minutes using smart filters  Huge saving for Quality Managers
Benefit: create
focused campaigns
in no time
Save a lot of time in
managing
campaigns

27. When Quality
really matters
www.xqual.com
Help Center:
https://xqual.zendesk.com