We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byDorian Braund
Modified over 2 years ago
Plugin Quality Check Penny Wyatt JIRA QA Team Lead Atlassian
Quality Assistance Help devs to deliver value to customers Testing and testing advice Bug prevention
Plugin Quality Process Make it work Make it lustworthy Make it maintainable Make it safe
Setting the Quality Bar Tradeoff between time, scope and quality Mismatched quality expectations - unhappy customers
Make it work “But I’ve already tested it, it works!” in the real world
Happy Path Fallacy “We’ll only worry about the happy path, for now” Only test the actions a normal, reasonable user would perform.
Happy Path Fallacy Quality bar defines what you fix, not what you test. OK not to support everything. Set customer expectations!
Valid Scenarios Sample Plugin Purpose-built but not contrived Completely unrelated to similar plugins on PAC! Only a short list, more detail on CAC
Valid Scenarios Different types of data Special characters Large data sets Long strings
Valid Scenarios Different browsers Layout issues Broken functionality Behaviour in unsupported browsers
Valid Scenarios Different use cases Session timeouts Deletions/Moves/Edits Anonymous access
Make it Lustworthy
User experience Guide users towards the actions they should do. Avoid empty boxes - use appropriate controls. Help them to avoid mistakes. Reading documentation should not be required.
Administration experience Clear flow for configuration Provide helpful error information Don’t show stack traces Use logging sparingly
Make it Maintainable
Manual and Automated Testing Manual testing Fast, effective, broad. Only tests the current state. Automated testing Scalable, sustainable. Takes time, limited assertions.
Automated Testing Good for long-term regression tests Optimise for: Scenarios most likely to break Integration with code out of your control Use page objects for UI tests for maintainability
Version Numbering Versions are constant A version number refers to one state of the code only. Never re-release a plugin with the same version number. 25
26 v2.5 Latest? Yes! v2.5 Help! v2.5 ??? v2.5 Argh! !!!!!!!!!
Version Numbering One version number means one binary. Always bump up the version number. 29
Make it Safe
How plugins break apps XSS Inserting user-supplied data into HTML without HTML-encoding it. Allows an attacker to gain control of the victim’s browser.
How plugins break apps Insufficient permission checking Exposing data to anonymous users Not respecting permission schemes
How plugins break apps Performance Synchronous external requests Unbounded memory allocation
Final check Made it work Made it lustworthy Made it maintainable Made it safe
#atlascamp TAKE-AWAYS Penny Wyatt firstname.lastname@example.org
1 Software Development Configuration management. \ 2 Software Configuration Items that comprise all information produced as part of the software development.
Introduction to ASP.NET development. Background ASP released in 1996 ASP supported for a minimum 10 years from Windows 8 release ASP.Net 1.0 released.
CS 5380 Software Engineering Chapter 8 Testing.
By Rick Clements Software Testing 101 By Rick Clements
MANUAL TESTING KS SESSION PRESENTED BY 26/11/015 VISHAL KUMAR.
DNN Performance & Scalability Planning, Evaluating & Improving : Part 2.
RMsis – v Simplify Requirement Management for JIRA
Learning Web Design: Chapter 4. HTML Hypertext Markup Language (HTML) Uses tags to tell the browser the start and end of a certain kind of formatting.
“Kuality” Assurance What does that look like? Scott Heise Indiana University KFS - Quality Assurance Manager Paul Sandoval University of Arizona KRA –
1 of 4 This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. © 2007 Microsoft Corporation.
Date : 3/04/2010 Web Technology Solutions Class: PHP Web Application Frameworks.
Systems Analysis and Design in a Changing World, 6th Edition
High Level: Generic Test Process (from chapter 6 of your text and earlier lesson) Test Planning & Preparation Test Execution Goals met? Analysis & Follow-up.
Top Five Web Application Vulnerabilities Vebjørn Moen Selmersenteret/NoWires.org Norsk Kryptoseminar Trondheim
Building Secure Web Applications With ASP.Net MVC.
Web Applications Testing By Jamie Rougvie Supported by.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Basic HTML Document Structure. Slide 2 Goals (XHTML HTML5) XHTML Separate document structure and content from document formatting HTML 5 Create a formal.
© 2017 SlidePlayer.com Inc. All rights reserved.