Professional Documents
Culture Documents
QATP
QATP
Notification API
ECY6489 Group4
Table of Contents
Table of Contents................................................................................................... 2 1. Introduction........................................................................................................ 4 1.1 Purpose......................................................................................................... 4 1.2 Overview....................................................................................................... 4 1.3 Definitions, Acronyms and Abbreviations.......................................................5 2. Scope of Testing.................................................................................................5 2.1 Product Overview..........................................................................................5 2.2 Product Risk.................................................................................................. 6 2.3 Test Coverage...............................................................................................7 2.4 Functional Requirements...............................................................................7 2.5 Out of Scope..................................................................................................8 3. Assumptions.......................................................................................................8 4. Test Deliverables and Schedules........................................................................9 5. Testing Approach..............................................................................................10 5.1 INSTALLATION / SMOKE TESTING.................................................................10 5.1.1 Objective...............................................................................................10 5.1.2 Entry criteria.........................................................................................10 5.1.3 Exit criteria............................................................................................10 5.1.4 Test suspension and resumption criteria...............................................10 5.2 UI / USABILITY TESTING...............................................................................11 5.2.1 Objective...............................................................................................11 5.2.2 Entry criteria.........................................................................................11 5.2.3 Exit criteria............................................................................................11 5.2.4 Test suspension and resumption criteria...............................................11 5.3 FUNCTIONAL / SYSTEM TESTING..................................................................11 5.3.1 Objective...............................................................................................11 5.3.2 Entry criteria.........................................................................................11
5.3.3 Exit criteria............................................................................................11 5.3.4 Test suspension and resumption criteria...............................................12 5.4 REGRESSION TESTING.................................................................................12 5.4.1 Objective...............................................................................................12 5.4.2 Entry criteria.........................................................................................12 5.4.3 Exit criteria............................................................................................12 5.4.4 Test suspension and resumption criteria...............................................12 5.5 PERFORMANCE TESTING..............................................................................12 5.5.1 Objective...............................................................................................12 5.5.2 Entry criteria.........................................................................................13 5.5.3 Exit criteria............................................................................................13 5.5.4 Test suspension and resumption criteria...............................................13 5.6 COMPATIBILITY TESTING..............................................................................13 5.6.1 Objective...............................................................................................13 5.6.2 Entry criteria.........................................................................................13 5.6.3 Exit criteria............................................................................................13 5.6.4 Test suspension and resumption criteria...............................................13 5.7 SECURITY TESTNG.......................................................................................13 5.7.1 Objective...............................................................................................13 5.7.2 Entry criteria.........................................................................................13 5.7.3 Exit criteria............................................................................................14 5.7.4 Test suspension and resumption criteria...............................................14 6. Test Environment............................................................................................14 6.1 Software and Hardware...............................................................................14 7. Test Cases........................................................................................................ 15 7.1 Notification API............................................................................................15 7.2 User Activation notification..........................................................................16 7.3 Listing latest items notification....................................................................17
1. Introduction
1.1 Purpose
The purpose of this plan is to define the project of Notification API, SQA tasks and responsibilities; provide reference documents and guidelines to perform the SQA activities; provide the standards, practices and conventions used in carrying out SQA activities; and provide the tools, techniques, and methodologies to support SQA activities.
1.2 Overview
This document contains the QATP for the Back-Talk. This plan establishes the SQA activities performed throughout the SDLC of the Notification API.
4
The goal of the SQA program is to verify that all software and documentation to be delivered meet all technical requirements. The SQA procedures defined herein shall be used to examine all deliverable software and documentation to determine compliance with technical and performance requirements. This document is presented in seven sections as follows: Section 1 identifies the system to which this SQA Plan applies; provides an overview of the system and its software functions; summarizes the purpose and contents of the SQA Plan. Section 2 describes SQA involvement in testing Section 3 describes the list of assumptions that this plan is based on, which will affect the scope of testing. Section 4 lists the major QA deliverables. Section 5 describes the information about the various types of testing conducted by the QA team. Section 6 lists the software and hardware required for the successful execution of the test plan.
2. Scope of Testing
2.1 Product Overview
Notification API is java library which support sending Email and SMS programmatically. It supports different types of Email server and SMS gateway configurations. Developers who are using Notification API for their development process will have number of advantages. The main advantage is reduce development time and increase the quality of programming codes. Developers can do the notification task without spending much more
time in coding. Learning curve of understanding the functionalities and their usages is very easy through the Javadoc provided to them. Under this project another four main components developed. They are User Activation notification, Listing latest items notification, SMS Bidding notification and business e-flyer notification. These components developed as a requirement of client. Each of this component used Notification API as the dependency. Mainly out of these four components, three components are newly developed and one component is improving the current process. User Activation Notification component is improving the existing process of the system using Notification API. It will enhance the coding standard and the performance of the process. Other than sending email to activate user, it will offer verify user through SMS. Listing Latest item notification is new component to the system. It will enable users to list highly selling item list through sending SMS to the system. System would response to the request of user searching latest selling items from the database. SMS bidding enable registered users to without logging to the system and bid and win the items available in auction site. This feature will improve the current bidding process, which is over the internet. Business e-flyer is developing to enhance marketing process of the client. In particular day or in particular time-period, client can automate sending eflyer to all registered users of the auction site. This might sent as either image or any other html document that mainly focuses on improves item selling and user attraction to the auction site.
Define technological Make email sending process stack which is support more effective and efficient any platform
6
UR002 UR003
UR004
UR005
UR009
Design more effective More reusable software system architecture component for email process model Supports send various types Divide architectural of email single, bulk, model into different attachments, etc modules Feasibility study to find Offer new SMS facility to user out way of integrating to bidding to an item SMS facility with existing system More effective communication link Use same SMS functionality between Notification to view an item list API and existing system database Divide architectural Supports single, bulk SMS model into different sending facility modules Scheduling system to send Integration of scheduler Email or SMS periodically with java library More effective software Finally design platform component which can be add independent java to existing project library Design overall project which should be not Supports current platform make any conflict with existing system
Requirement Definition Common library facilitate email and SMS functionalities With newly developed library modified existing user activation process Software component to list all latest items through SMS Software component to place a bid through a SMS Software component to support send bulk email as marketing flyer
3. Assumptions
For System testing, the Development team has completed unit and integration and met all the Requirements. User Acceptance testing will be conducted by End-users. Use cases are approved by test lead. Test scripts are developed and approved. Test Team will support and provide appropriate guidance to Developers to conduct testing Major dependencies should be reported immediately after the testing kickoff meeting. Delivery of the product is in format that the test team can check it into SVN. The delivery of the product to production contains all setup, etc., that is necessary for optimum performance in the production site. Project sponsors, business and technical, will provide actionable guidance on defect prioritization and resolution
Documents
QATP
Test Cases
Test Cases
Task name Test Planning Review Requirements documents Create initial test estimates First deploy to QA test environment Functional testing Iteration 1 Second deploy to QA test environment Functional testing Iteration 2 System testing Regression testing UAT Resolution of final defects and final build testing Deploy to Staging environment Performance testing
Start date
Finish date
Effort 5 days 1 day 1 day 1 day 7 days 1 day 7 days 2 days 2 days 5 days 1 day 1 day 1 day
5. Testing Approach
5.1 INSTALLATION / SMOKE TESTING
5.1.1 Objective
The installation testing will validate that: Proper program are placed in the QA server Appropriate test data is available The installation guide is prepared and followed for installation the software
5.1.2 Entry criteria
QA environment is setup with necessary hardware, operating system and supporting software Installation guide with step by step installation process is created by the development team All the software, tools, databases stored procedures and scripts required for successful installation are delivered to QA Accuracy and completeness of the installation guide is verified Installation guide conforms to portability requirement so that a system that is to be moved from one operating environment to another must be adequately documented to identify both areas of potential changes and the operating characteristics Integrity of program files is verified Smoke test successfully completed
The installation test will be suspended if one or more of the following is encountered If the installation guide does not have the necessary steps for performing the installation Files needed for installation are not included in the release Necessary files are not managed in configuration control Installation testing will be resumed after the suitable changes are made
10
Usability testing will assess the user interface for: Compliance to UI guidelines Ease of use, navigation and understanding Adherence to prototype / Wire Frame / Visio diagram and requirement
5.2.2 Entry criteria
Application is successfully installed UI is rendered on client machine Developer release notes provides scope of testing and known issues No critical and high severity defects are open All known issues are documented Not applicable
Functional testing is done by creating test condition for use in evaluating the correctness of the application. It is designed to ensure that system requirements are documented in section 2.4. Code is peer reviewed and unit tested. The entire high and critical unit testing defects are fixed. Plan for closing all low and medium severity defects should be documented and unit testing result are published Application is successfully installed Smoke testing is successful Developers releases notes provide scope of testing and known issues No critical and high severity defects are open All known issues are documented
11
Testing will be suspended if: Showstoppers or critical issues, which prevent the testing of major functionality, are encountered. Functionality is unstable, i.e. too many non-reproducible defects are encountered Testing will be resumed when the showstoppers are fixed.
Regression testing and retesting cycles are performed to ensure that: Changes and defects fixes do not adversely impact previously released software There is an increased stability of the software Defects in previous releases have been addressed according to the functional requirements Application is successfully installed Smoke testing is successful Developer release notes are provide with scope of testing, known issues, list of defects fixed, information about other parts which might have been affected by the defect fixes. No critical and high severity defects are open All known issues are documented
Testing will be suspended if: Showstoppers or critical issues, which prevent the testing of major functionality, are encountered. Functionality is unstable. i.e. too many non-reproducible defects are encountered. Testing will be resumed when the showstoppers are fixed.
The performance testing is done to verity whether the application meets projected volume and response time requirements specified in section 2.4
12
The functional testing result does not have any high or critical defects. Performance test scripts are ready for use The required successfully performance measurement have been obtained
Performance testing is suspended if showstoppers are encounter during performance testing Testing will be resumed when the showstoppers are resolved.
A compatibility test insures that the application works with differently configured systems based on what the users have or may have. When testing a web interface, this means testing for compatibility with different browsers and connection speeds.
5.6.2 Entry criteria After successful completion of functional testing and all required non-
functional testing
No critical and high severity defects are open All known issues are documented
Compatibility testing is suspended if showstoppers are encountered. Testing will be resumed when the showstoppers are resolved
To test the application and system level accessibility correctness. Verify that actor can access only those functions or data for which their user type is provided permissions. System Level Security: Verify that only those actors with access to the system and applications are permitted to access them Product is stable in terms of Functionality and Performance
13
Security testing is suspended if showstoppers are encountered. Testing will be resumed when the showstoppers are resolved
6. Test Environment
6.1 Software and Hardware
Machine Purpose Software Requirement Hardware Requirement Supermicro 5014C-MT 1U Rackmount 3.0GHz Pentium 4 CPU with 1MB Cache 8GB RAM 1TB Seagate SATA Drives configured for RAID Intel Pentium 4 2.8GHz 1MB CPU Cache 1GB RAM 200GB IDE HD HP Color LaserJet CM1312nfi MFP Quantity
Application installation
Client Computer
Ubuntu OS
Laser printer
14
7. Test Cases
7.1 Notification API
ID Description Prerequisite SMTP server configurati on should be loaded Steps Calling sendEmail or sendGroup Email method Calling sendEmail or sendGroup Email method Calling sendEmail or sendGroup Email
15
Input subject sender email recipient email(s) message No Data or invalid subject sender email recipient email(s) message Either one invalid subject sender email recipient email(s)
Output
Send email with valid four parameters NA00 (subject, 1 sender, recipient, message) Send email with invalid four NA00 parameters 2 (subject, sender, recipient, message) NA00 Send email 3 with either one of invalid four parameters
SMTP server configurati on should be loaded SMTP server configurati on should be loaded
(subject, sender, recipient, message) Send SMS with valid two NA00 parameters 4 (recipient, message) Send SMS with invalid NA00 two 5 parameters (recipient, message) Send SMS with either one of invalid NA00 two 6 parameters (recipient, message) SMS gateway configurati on should be loaded SMS gateway configurati on should be loaded SMS gateway configurati on should be loaded
method Calling sendSMS or sendGroup SMS method Calling sendSMS or sendGroup SMS method Calling sendSMS or sendGroup SMS method
message
UA00 1
UA00
Signup with
System up
Complete
16
and running
signup form
UA00 3
invalid userName, password, firstName, lastName, gender, dob, addressLin e1, addressLin e2, addressLin e3, email, mobileNo, Either one of invalid userName, password, firstName, lastName, gender, dob, addressLin e1, addressLin e2, addressLin e3, email, mobileNo, Username, password
message displayed
UA00 4
Log in with given user name and password Log in with invalid or no user name and password
UA00 5
Activate user account by click Activate link in activation email Activate user account by click Activate link in activation email
Username, password
category list with valid short code LI002 Request item list with invalid short code Request item list with valid category Request item list with invalid category
and running System up and running System up and running System up and running
code and send SMS Enter short Invalid or code and no short send SMS code Enter category code and send SMS Enter category code and send SMS Category code Invalid or no category code
message including category list No response Response message including item list No response
LI003
LI004
SB001
SB001
SB003
SB004
Enter valid short code to get current bid User amount of should item activate SMS bidding System up and Enter invalid running short code to get current bid User amount of should item activate SMS bidding System up and running Enter bid amount higher User than current should amount activate SMS bidding Enter bid System up
Item list Enter short with code to current bid get item amount list SMS
Itemcode,
amount equal to current User amount or less should than current activate amount SMS bidding
and running
bid amount
BE001
title, Image or HTML file location, User email list excel sheet
BE002
title, Image or HTML file location, User email list excel sheet
BE003
title, Image or HTML file location, User email list excel sheet
19