|
| Software
Testing |
|
|
|
|
|
|
| |
| Latest
Events |
|
|
|
"Workshop on Methodologies for Effective Software
Testing" |
|
April 15-16, 2011- Bangalore |
|
|
|
For more details
contact us |
|
|
|
|
|
|
Software Testing - Technical Program |
|
|
|
Workshop on
Methodologies for effective Software testing
April 15-16, 2011, Bangalore
Venue : Hotel Regaalis (Old
Hotel Rama International)
Lavele Road, Bangalore
------------------------------------------------------------------------------------------------
Day 1 – Risk Based
Testing (April 15, 2011)
|
Topic |
Details |
Time |
Duration |
|
Registration |
------------- |
09:00 am |
30 min |
|
Risk
Based Testing – Process
(Session 1)
|
-
Introduction to ‘conventional’ testing strategies
and their shortcoming
-
RBT as part of testing/development cycles –
addressing the tradeoff between ‘quality’ and
time/resources available.
-
Relationship between test-cases (their types,
density/number, and risks
-
Role of automation in RBT
The session will end with the participants getting
introduced to a RBT process framework along with
enabling tools that they can use.
|
09:00 am |
45 min |
|
Experiences with RBT
(Session 2)
|
Case Study (Case 1 and Case 2) based informal
discussion on what/why risk-based testing (RBT).
- Discussion on the role of RBT based-on
participants’ experiences with
RBT
- Facilitate identification of some of the
perceived/real risks
- Informal analysis of the risks – their impact and
likelihood of occurrence
|
10:15 am |
30 min |
|
Coffee / Tea Break (15 min) |
|
Risk
Identification and Analysis
(Session 3)
|
Facilitated discussion
using Case 1 & 2
-
Risk Identification techniques:
- Consideration of factors such a
code/algorithmic complexity,
people involved, visibility, usage frequency, time, bug history,
technology in use, coverage metrics, etc.
- Quality considerations –
functionality, reliability, usability,
efficiency, maintainability etc.)
-
‘Units’ with which risks will be associated –
functions, classes, modules, use-case, etc. –
Some ways to select appropriate units for a
given project.
-
Risk analysis – estimation of probability of
occurrence and impact. Risk Prioritization.
|
|
|
|
|
|
11:45 am |
60 min |
|
Lunch Break (45 min) |
|
Risk
Based Testing
(Session 4)
|
Facilitated discussion
on
-
Mapping risk profile to test strategy
-
Choice of test cases, scope of regression
tests, based on risk profile
-
Ways to identify areas of testing that are
worthwhile automating based on the
risk-profile.
|
Discussion will use Case 1 and Case 2 for
illustrations along with the framework and tools
that the participants would have briefly been
introduced to in Session 2. |
13:30 pm |
45 min |
|
Hands-on: Mapping of strategies and case studies
from Case 1 & 2 |
14:15 pm |
60 min |
|
Coffee / Tea Break (15 min) |
|
Risk Based Testing
(Session 4) |
Tool Demo using Quality
Center (HP) |
15:30 pm |
45 min |
|
RBT Results - Reporting
and Metrics
(Session 5)
|
-
Risk-based failure/bug characterization
-
Risk based metrics – reconciling risks, tests
carried out and failures detected.
-
Estimation of residual ‘risk’ and defects based on
standard defect metrics, the test results and the
risk profile
-
Feeding the test results back into the
risk-profile
-
Client perception management with RBT – what and
how to report ‘quality’ and ‘test’ metrics to the
client.
|
16:15 pm |
60 min |
|
Wrap up |
Recap, Discussions, Q&A
|
17:15 pm |
30 min |
Day 2 – Risk Based
Testing (April 16, 2011)
|
Topic |
Details |
Time |
Duration |
|
OAT – Introduction
(Session 1)
|
-
Uniqueness of the approach, understanding the
concept and statistical perspective with its
advantages
-
Case study based discussion for a testing scenario
to bring out the above concepts and advantages
-
Algorithm for Orthogonal Array and its
characteristics
|
09:30 am |
60 min |
|
OAT –
Test Design
(Session 2)
|
-
Design of test cases using OATS for various
product / application scenarios
-
Demo of an Excel based tool for generation of test
cases using Orthogonal Array
-
Hands on: Developing test cases for various
scenarios
|
10:30 am |
75
mins
(including 15 mins for coffee/tea break)
|
|
OAT – Test Design
(Session 3)
|
|
11:45 am |
60 min |
|
Wrap up |
Discussions, Q & A |
12:45 pm |
30 min |
|
Lunch Break (45 min) |
|
Security Testing
(Session 1) |
-
What is Security
-
Grasping the
fundamentals of Security flaws
-
Vulnerabilities and
the anatomy of an attack
-
Some proven
application security principles
-
The mindset needed
for Testing the Security aspects of a web
application
|
14:00 pm |
45 min |
|
Security Testing
(Session 2) |
|
14:45 pm |
120 min |
|
Coffee / Tea Break (15 min) |
|
Security Testing
(Session 3) |
Automation
Possibilities and demo |
16:45
pm |
45 min |
|
Valedictory |
Discussions, Q & A |
17:30 pm |
30 min |
|
|
|
|
Fast Facts |
|
|
|
Dates:
April 15-16, 2011 at Bangalore
Delegate Fees:
Rs. 10,000/- (Service Tax of 10.3% extra)
Discounts:
10% Early Bird Discount (payment to be received by March
31, 2011)
10% for groups – 5 delegates or more from the same company
Maximum
discount across all combinations restricted to 15%
|
|
|
|
| |
|
For
delegate registrations, contact:
VANN Consulting
Pvt. Ltd.
Bangalore
Phone:
080-2520-1625Mobile:
+91 8762-315 315
E-Mail:
info@innovate-it.in |
| |
|
|
|
|
|
|