Testing Types Presentation

  • 1,153 views
Uploaded on

need download of the same login to www.stqa.org or keep me mailed

need download of the same login to www.stqa.org or keep me mailed

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,153
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Real life scenario- An assumption ATM SHOPPING MALL POS CEO,CFO,STAKE Bank VISADB Network cloud HO ?????? ????? ???? Network managers ????
  • 2. Real life scenario- An assumption ATM SHOPPING MALL POS CEO,CFO,STAKE Bank VISADB Network cloud HO Ease of use No loss of network connectivity Credit of exact amount withdrawn Report of transaction Fast data entry Faster processing of items Accuracy of items and its prices Invoicing without arithmetic errors High productivity from sales persons Higher sales, HIGH revenues balance sheets by EOD Lower operating expenditure ROI Customer satisfaction for repeated business Proper interfaces between DB’s and ATM No downtime Faster authentication process 100’s /1000’Sof concurrent users Sufficient Network band width Huge DB servers for multiuser-multitransactions Heterogeneous servers/systems Data integrity Security DB/Network managers High quality products/items On time delivery Within budget/lesser cost Service after sales ROI Lesser maintenance costs -------- Good ambience thru Good communication Well established systems For customer service
  • 3. Observations
    • As application changes, requirements also changes.
    • All expectations are not applicable to all systems.
  • 4.
    • Various systems/applications/products
    • MIS/ERP APPLICATIONS
    • EMBEDDED SOFTWARE
    • SYSTEM SOFTWARE
    • UTILITIES
    • DIAGNOSTIC SOFTWARE
    • S/w packages like test tools, RDBMS etc.,
    • Data communication s/w
    • Process control s/w
    • Application Integration s/w etc.,
    • Entertainment/edutainment s/w
    • Mission critical/real time s/w
    • Software design models
    • Web applications
    • Client-server
    • Distributed
    • Legacy systems etc.,
    • Various Requirements/expectation
    • /objectives
    • Quality requirements
    • CORRECTNESS
    • USABILITY
    • INTEGRITY
    • EFFICIENCY
    • RELIABILITY
    • SAFETY
    • SECURITY
    • PORTABILITY
    • REUSABILITY
    • INTEROPERABILITY
    • EXTENSIBILITY
    • SCALABILITY
    • MODULARITY
    • MAINTAINABILITY
    • TESTABILITY
    • FLEXIBILITY
    • Test requirements
    • Defect free;100% test coverage;
    • 95% code coverage; max 3-4 bugs
    • ;Robustness
    • Business requirements
    • High performance;
    • Ease of doing business;
    • Reports; benefit to bussiness
    • Customer expectations
    • Stated :
    • High quality product
    • Competitive price
    • On time delivery
    • Maintenance
    • Implied:
    • Good communication channel
    • Highly technical skills
    • Process oriented
    • Value addition like BPR etc.,
  • 5. How to test a pen? How to test a calculator? How to test a LIFT?
  • 6. Types of testing
    • Levels of testing
    • Black box
    • White box [ statements,branches,paths, code coverage, cyclomatic complexity]
    • Regression [ Retesting after fixing the bugs found during testing and also when there is change in the test envi. ;impacted portions of the code after fixing the bug is retested;
    • Gorilla
    • BVT/Smoke/Sanity [quick-and-dirty test that the major functions of a piece of software work without bothering with finer details]
    • Performance[ focus on p.parameters transaction response time,cpu utilization,network utilization]
    • Stress/load [at or beyond the limits of its specified requirements to determine the load under which it fails and how]
    • Volume: [ incremental data load on system by reducing resources]
    • Alpha:[ by eu’s or others but not by dev/test;
    • Dev is near to completion; minor design changes]
    • Beta: [ dev & Test completed; final bugs before final release; same as above]
    • Functional [conforms to its specifications and correctly performs all its required functions ]
    • Recovery : [ Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication/ntwork, or power out conditions.
    • Globalization [ international support without data loss or display problems; with any culture or locale]
    • fr-france;fr-canada;fr-swisss
    • Localization [ particular culture or locale]
    • Security [ improper logins; injections, privilege elevation]
    • Compatibility [ different browsers, OSs, and hardware platforms]
    • Configuration [ broad range of hardware/peripheral equipment configurations as well as on different operating systems and software]
    • GUI/Front-end [ attributes of GUI objects; event driven inputs; container forms]
    • End-to-End [ Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate. ]
    • UAT [ after SIT completes, by customer/user; against requirements; in production with real data ]
    • Usability [to measure the product's ease-of-use, task time, and the user's perception of the experience; Testing the ease with which users can learn and use a product.]
    • Instrumentation [ like comments,msgbox to know program behavior at runtime]
    • Ad Hoc Testing : Testing carried out using no recognized test case design technique