View
367
Download
3
Category
Tags:
Preview:
DESCRIPTION
view webinar: http://www.eurostarconferences.com/community/member/webinar-archive/webinar-74-test-script-free-validation-in-a-regulated-environment-kanban-style Software development and testing practices have gone through a revolution since Agile came into the scene. Buzz words such as scrum, user stories, Kanban, lean and test driven development are all the rage now. Many of these Agile practices have shown to improve the overall quality of the software yet it can be very hard to implement them in a heavily regulated environment. This presentation will discuss an experience in applying a lean and just in time test approach while working in the Pharmaceutical Industry where detailed test documentation and providing evidence of the testing are mandatory requirements from clients. By taking principles from Acceptance Test Driven Development and Kanban techniques, the presentation will show how producing a detailed requirement specification can drive the test execution without the need for detailed test scripts. By automatically generating traceable test evidence using video recording tools, the tester can save time on documentation and invest the time saved on performing further testing.
Citation preview
www.excointouch.com
Andy Glover
EuroSTAR 2013
KANBAN STYLE
TEST SCRIPT-FREE VALIDATION IN A REGULATED ENVIRONMENT:
@esconfs #esconfs
Agenda
History
Mentality
Ideas
Case Study
History
Pitfalls
Ideas Freedom
@esconfs #esconfs
Go to Jail
@esconfs #esconfs
Do you expect better testing practices in a heavily regulated environment?
Question for the audience
@esconfs #esconfs
Different Test Phases
A formal process V. An informal process
• Formal test process near the end of the project. Highly detailed and rigid process.
• Informal test process throughout project. Flexible, low detail.
@esconfs #esconfs
Reality: Informal Test Process
Hard to describe Not managed Seems random at times
@esconfs #esconfs
Reality: Formal Test Process
• Test Plan– Test Scripts
• Traceability Matrix– Test Report
– Issue Logs
• Screen Shots• Review, Review, Review
• Sign and date
@esconfs #esconfs
Agenda
History
Mentality
Ideas
Case Study
History
Pitfalls
Ideas Freedom
@esconfs #esconfs
What’s the problem
Testers mind-set:
Pass an audit!
@esconfs #esconfs
Tester’s Mind Set
@esconfs #esconfs
Ideas, Suggestions
History
Mentality
Ideas
Case Study
History
Pitfalls
Ideas Freedom
@esconfs #esconfs
Every project is different
FDA do not mandate a test approach or techniques
Every software development project is different
Testing starts from day one
Request testability requirements
@esconfs #esconfs
Manage all the testing
Manage the informal testing
Manage the testing in sessions
Add Variety Not just Requirements based
testing
@esconfs #esconfs
Don’t settle down
• Good testing is hard
• Software Development (and testing) is new(ish)
@esconfs #esconfs
Learn
Learning doesn’t stop at the end of conferences [or webinars]
Learn from other testers in the same industry as well as other industries
Books, magazines/articles, blogs, forums, exercises/group sessions
@esconfs #esconfs
It’s all about the evidence
Highly detailed test scripts are common in the industry
@esconfs #esconfs
It’s all about the evidence
“Abundant, quality evidence mitigates your other problems”- Griffin Jones 2012
Video shows software working in specific scenarios
@esconfs #esconfs
Video example??
@esconfs #esconfs
Merge the [testing] phases
Agile
Working software overcomprehensive documentation
@esconfs #esconfs
Automation
• Automate as you go within the sprint• Automate only what needs automating
– Focus on checking the software• Add to the automated regression suite• Work with the developers as one team• Use the automation to validate product:
– Build reviews/checks around the automation– Produce screenshots & reports from the automation
@esconfs #esconfs
Kanban… or is it ATDD?
History
Mentality
Ideas
Case Study
History
Pitfalls
Ideas Freedom
@esconfs #esconfs
Put your hands up
Admit you do Requirements Based Testing- i.e. Checking every specification item
From a Requirements or Specification doc:
Req ID Requirement Test Result1 Valid User can login to the system Pass2 Invalid passwords will be rejected Pass3 User will be locked out following 5 invalid passwords Pass
@esconfs #esconfs
OLD PROCESS
@esconfs #esconfs
NEW AND AMAZINGLY AWESOME PROCESS
@esconfs #esconfs
NEW AND AMAZINGLY AWESOME PROCESS
@esconfs #esconfs
WHO OWNS QUALITY?
@esconfs #esconfs
SOAP OPERA TESTING
@esconfs #esconfs
SOAP OPERA TESTING
@esconfs #esconfs
Summary
Highly regulated environments can develop and learn from other industries
Suggestions on new processes/tools
Testers must keep learning and developing skills
Case Study
THANK YOU
www.excointouch.com
Andy Glover
Head of Testing at Exco InTouchAndy.glover@excointouch.com
Software Testing community:Blog: http://cartoontester.blogspot.comTwitter: @cartoontesterI regularly contribute on STC’s The Testing Planet
www.excointouch.com
EXCO INTOUCH
Our mission is to improve clinical and healthcare outcomes through simple, effective and engaging
patient communication
Exco InTouch is a privately owned & managed company, established in 2004
Operational offices in UK, USA and CanadaStudies conducted in 85 countries with over 750,000 patients
@esconfs #esconfs
Questions
?
Recommended