ImageVerifierCode 换一换
格式:PPT , 页数:33 ,大小:300KB ,
资源ID:377964      下载积分:2000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
注意:如需开发票,请勿充值!
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-377964.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(Acceptance Testing for ROME.ppt)为本站会员(roleaisle130)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

Acceptance Testing for ROME.ppt

1、Acceptance Testing for ROME,Pete Castle Test & Quality Manager,Agenda,What is software testing/ Who does it? Why software testing is important Some fundamentals of testing Test Plans & Scripts Sample Testing Techniques,What is software Testing?,“Software testing is an empirical technical investigati

2、on conducted to provide stakeholders with information about the quality of the product or service under test” Professor Cem Kaner - Director of Florida Techs Center for Software Testing Education & ResearchEmpirical - derived from experiment, experience, and observation Technical - Having special sk

3、ill or practical knowledge Investigation - A detailed inquiry or systematic examination,Why testing is Important,All Software has defects (bugs) All software products are prototypes (in my view) Software products are getting larger and more complicated - Vista 40% larger than XP over 50 million LOC

4、Software Engineering is not as mature as other disciplines e.g. Civil Engineering Software is written by people people make mistakes Software testing looks to find the most important defects as early as possible increasing confidence that the software meets specification,Whos involved in testing?,Re

5、quirements Analysts Inspections, Peer Reviews Developers Code Inspection, Unit Testing Testers System & Integration Testing Trainers Training materials production Users User Acceptance Testing Project Managers Scheduling, Resourcing, Risks, Issues, Defect Stats Everybody is responsible for quality -

6、 NASA,Fundamentals of Software Testing,Software testing needs planning, tests need specifying, once executed they need results recording, and post completion should be easily auditable,The importance of a planned approach,Important to map out a strategy that will give the greatest level of confidenc

7、e in the product Ad hoc testing may find errors, but may not be cost effective Testing should focus on areas where defects are most likely All testing should have a reason Question “Is a test that doesnt find an error a good test or not?” Essential to plan what needs to be done and then itemise how

8、it is to be achieved.,Testing Mantra,Mantra - Spiritual conduit, words or vibrations that instil concentration in the devotee.Test as early as possibleGather as much knowledge of the application under test as possibleLook for vulnerabilitiesBuild Bug Taxonomies (Classification)Use Quicktests (and pu

9、blicise the fact),Testing Mantra,You can always think of another test but should you? Concept of Good enough Testing Practicality over dogma Everybody has responsibility for shipping the productRecord all tests/defects/issues/recommendationsTesters are not the sole arbiters of quality Testing only s

10、hows problems exist not their absenceNever, ever, ever make it personal Defects are issues with products and process not people Good working relationship is essential for good products,Document Hierarchy - Test Plan,What is a Test Plan - 1,Test plan is tool to help plan the testing activity product

11、to inform others of test process Includes Document control Objectives Scope Approach Schedule, Priorities, Deliverables, Resources, Responsibilities Risks/Contingences Sign-off/Approval,What is a Test Plan - 2,Produced by Test Lead/Project Manager Published to Project/Programme Not constrained by fo

12、rmat living document Enough information to be used by anyone to test the product,Rome Test Plan,Ready for review Written by Tim Wells,Document Hierarchy -Test Scripts,Test Scripts,Test Script - Is a collection of test cases for the software under test (manual or automated) Test Case - A set of input

13、s, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.,Pre-conditions/Information,Browsers IE, Firefox, Safari O/S Linux, Windows Access Control Logins, Roles Test Data

14、 requirements Date/Time considerations Other document references,Example Test Script - 1,System Test of input of numeric month into data field,Example Test Script - 2,Example Test Script - 3,Test Scripts,Readable Accessible Usable by anyone standards Can vary depending upon the type of testing being

15、 undertaken,Testing Techniques,Quicktests Negative Testing Integration Testing,Techniques 1- Quick Tests,Quicktests - Investigation more important than ConfirmationA quicktest is a cheap test that has some value but requires little preparation, knowledge, or time to performFocus on common coding err

16、ors,Techniques 1- Quick Tests,Things that have failed before Defect data Tab order (particularly when adding new functions) Addresses (BFPO, new Post Codes) Short cut keysBoundaries Ages, Dates, Values, Increments, Page BreaksInterrupts, Duplications, Ordering of tasks Generate Order before setup no

17、 cost codes, cost centres, suppliers, budgets Exit/Interrupt before completionConsume resource (Dog Piling) Never close a window Never exit an option,Techniques 1- Quick Tests,Force all error messages Informative messages - Spelling Debug information?Capacity/Files Files to fill all available space,

18、 large files, empty files, incorrect formatDependencies e.g. same student many functions Integration QuicktestComparisons screens, data, reports Tools e.g. Beyond Compare, Screen Capture, Redgate Toolset, InCtrl3,Negative Testing,Testing the system using negative data to generate exceptions that cau

19、se the software to fail Going against knowledge of How the system should work For Example - Testing the password where it should be minimum of 8 characters - so test it using 7 and 9 characters Emphasis on breaking not confirmation,Negative Testing,Embedded single quote and other special characters

20、e.g. Johns Car, John & Erin, 99%, Strae (German Addresses) Required Data Input Dont Field Size Shoe test (also Quick Test) Field Types Characters in numeric field Boundaries (Upper/Lower) underage job applications, 101 lines on an order with a maximum of 100 lines Invalid dates e.g. 31/04/08 Address

21、es BFPO, Hong Kong Addresses, New Post Codes Web Session Testing Access web page but not logged in Switch off during upgrade what happens, does the application know there is a problem?,Integration Testing (In the large),“Testing performed to expose faults in the interfaces and in the interaction bet

22、ween integrated components and products” Sue Myler Integration Team Lead Usually scenario based rather than low level test cases Relies upon testers having system knowledge & testing expertise ability to think outside of the box, develop new tests during testing Relies on successful unit, integratio

23、n in the small and system testing Can mimic business processes,Integration Testing (In the large),Integration Test Cases 3 Applicants 1 applies for 1 post 1 applies for 2 posts - also applies for the same post twice (by accident) 1 applies for 3 posts do their records appear correctly across ROME De

24、lete a Vacancy what happens to that applicant records?,Integration Testing (In the large),Short list applicant for post he entered twice, deleting one application Invite for interview but candidate withdraws Candidate then re-applies Data exported, ROME updated, then re-exported, does data appear co

25、rrectly in target application,Test Scenarios,Review,Software Testing is important for increasing confidence that the software meets specification To get the best results from testing certain fundamentals should be followed Testing is part of software development Different software testing techniques

26、 enhance our ability to test Many different types of software testing exist which we can combine into single test cases/scenarios,Test Example Data Entry Screen,Create Test cases to negatively test (break) the data entry screen,Next Steps,ROME - Kick off meeting Testing required who/when Test Script Template Mantis - Issue/Defect Logging,

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1