Home

Distributed Polling System Test Plan

image

Contents

1. Test Plan Sr Test Specification Description Deliverable No File name Phase 1 DPS test Specification defines test cases for the Implementation specification features to be tested identified in the Phase 9 Risks and contingencies In the testing no real important data should be used as in testing phase a bug can occur which could lead to the data loss Distributed Polling System Test Plan
2. Supervisors e SCORE reviewers 1 4 System Overview Overall DPS interfacing architecture Figure 1 1 System Interface Details delineates the complexity of testing of the whole system Web DPS application is the custom developed front end web based application responsible for fulfilling major functionalities of DPS Figure 1 2 Layered Architecture Stack of web DPS Application Whereas SMS Gateway and Email server are the underlying applications responsible for fulfilling DPS product functionality i e integrated solution by sending email SMS notification and receiving responses to from the respective recipients ks Single Step Parallel Steps Multiple Web DPS application Step Step 2 ep Invoke API using XML over HTTP SOAP over HTTP Step 5 Receive member s SMS response Poll an event to intimate members Step 6 Middleware Archive the event received by Middleware for tracking purposes JBOSS Archive the event received Dy Middleware for future reference Step 4 Email notification to members Email server Step 5 Poll response emall from server Figure 1 1 System Interface Details Distributed Polling System Test Plan 3 e amp mug FES LGU Laye ay ES Business Logic and integration layer Database Layer Figure 1 2 Layered Architecture Stack of web DPS Application 1 5 High Level Test plan
3. considerations Following are the aspects in our considerations and analysis to proceed with test plan e Do we have any migration plan from legacy applications e Do we have stand alone applications testing requirement e Do we have system s integration testing requirement Our analysis derives that it s a brand new development for DPS and no legacy data migration is reguired to our newly developed applications like existing user accounts to web DPS existing email domains and accounts of Email of DPS As web DPS is a custom developed application and will be fulfilling major functionalities of DPS we need to have stand alone application testing reguirement for web DPS Email server and SMS Gateway are the subsidiary applications that are required to fulfill the product s behavior and functionality we need to perform integration testing by invoking these two target applications from middleware layer for reguest interface Now there are two ways of invoking these two target applications e Simulate from Jboss middleware layer as if actual data is flowing from web DPS application without any help from web DPS application e Perform the actual data entry in the web DPS application GUI and submit that data which in turn will trigger the middleware interface to invoke target applications Similarly for response interfaces email server and SMS gateway will act as source and web DPS as target application 1 6 Critical Success Factors Follow
4. pre requisites for testing of a particular interface in DPS From integrated product perspective Figure 1 1 System Interface Details depicts the required interfaces and from web DPS stand alone application perspective it s the communication interface among each layer as depicted at Figure 1 2 Layered Architecture Stack of web DPS Application Our project deliverable DPS Design Description Document specifies the use cases at high level that portrays the entry and exit criteria for interface testing requirement for system s integration from business process perspective as below For Example Use Case 1 Goal Intimating members with poll details through SMS and email Actors SMS Gateway Email server DPS Application A E As soon as an event is triggered in the DPS EVENT TABLE located at DPS Triggering Event application database Entry Criteria Once a poll is created at DPS application Exit Criteria Successful sending of SMS EMAIL and status update at DPS ARCHIVE TABLE Distributed Polling System Test Plan 6 ar G a FS3 As soon as an event is inserted in DPS EVENT TABLE a JDBC listener that is Process Flow always polling this table picks up the event and send it to integration ESB enterprise service bus where a service is subscribed to that event Success When all the steps mentioned in the Business service flow diagram are successfully Conditions executed Fai
5. 2 SOE 2 mince IEI FES Distributed Polling System Test Plan Version 1 0 Distributed Polling System Test Plan 1 ar ha Uy Sy er FS Table of Contents 1 INTRODUCTION wissaescsesvccsscesencescecovevacucececncucnussucctoncouvetundseneeta NANUN NN ON ANNON NANOANS NNN NA UNNA ONT NN DAN NNN INNON VAN iaiia 3 1 1 PURPOSE OF THIS DOCUMENT cional dl didas lic 3 1 2 SCOPE OF THE DOCUMENT avaiicissiaianzasssdbacscesaacstabcanabadaavadsaieabooeddedsadeeduavadauvadsateabiaecdedeadeeayavadaudadsieeabiceddacaabends 3 1 3 TARGET AUDIENCE vs latvs vastaus aran suave sc asini av Einara aN sence dene suet ab uccudeuaueveawscueaecue seevabusduaeedvaveneasens 3 1 4 SYSTEM OVERVIEW dass 3 1 5 HIGH LEVEL TEST PLAN CONSIDERATIONS ccssssesecccccccceessseceecceeeeusessecceceeceeeuuseceeseeeeeuansseceeeeeseaeanseceeeeeeesnagens 4 1 6 CRITICAL SUCCESS FACTORS nasi siccacecisarsisatees dd sasaseasadvadhosadnassativadanesavesdadsaaecbadavanalie facsaswesaevaibevadasuaabinadonesecwe 4 Z TESTING SCOPE A A E E E T E 5 2 1 WEB DPS STANDALONE APPLICATION ssseseeceeccceesssseceecceeceusessecceseeceeesnseeceseeseeuaessecceseeeeaeaeseceeeeeseeuansseeeeseees 5 2 1 1 Web tier tostinasemsseansoakakt eikai st ass raataa NA Oahu an A A EE 6 2 1 2 Database and business tier testing cccccccccesssscscccessesssseesccsesseesseescccseseessuscecseseeessaseccsssesssaeseeess 6 3 TEST ENTRY EXIT CRITERIA sissciccsccccssssesscscccaccctesocsss
6. E 9 7 1 DEVELOPERS aa rsae vahan de e e ed ae roca d 9 7 2 USER REPRESENTATIVE ssicesascvccvsvascesdanabessovevuavatcnadsdwedcesdncange NEEE Ta va chagabge sp uavisnt OSTO N KUNA NEN eies aea inira 9 8 TEST DELIVERABLE iii saasa aan aava aa ansaa neNTa N oN On an OO Usina RON NOU ON NNUONNUONNNANONNUKN ANNA NUNN 9 8 1 o osatisiseatn scacnbasadanvanbedeepeauuvevis KaLKNENANNVAN MN Vaa PUUUP NSK A 9 9 RISKS AND CONTINGENCIES 1i5i5ssam saassahasaavousaua ansa psoe ionan oaos OOSNNONDONN NEN NES SSN NUNTSNNA RUN AUS SSNU UNS UNA KUN NNUNNENSSINOEN 10 Distributed Polling System Test Plan 2 ea Gy M LARDALEN UNIVERSITY Fee 1 Introduction This document is the Software Verification and Validation Plan for Distributed Polling System DPS The project is conducted as a part of SCORE contest and distributed software development course for the year 2008 2009 1 1 Purpose of this Document This document describes methods and techniques that the DPS team is following to verify and validate the product being developed against customer s requirement The document will help us to ensure that at each phase of product s development we follow our defined testing techniques and processes 1 2 Scope of the document This document describes the test plans and the test design techniques which are used to verify the DPS system 1 3 Target Audience The below is the list of intended audience for this document e DPS project team e Customers and
7. ame Interface Name Web DPS Rh NA means testing of stand alone web DPS functionality Managing members Logging into web page Managing members Managing member s personal details Intimate poll details Creating poll Intimate poll details Opening and closing poll information Intimate poll details Deletion of poll Intimate poll details View poll results Verdict on Voting Vote Calculation Verdict on Voting Vote announcement on deadline Verdict on Voting Vote announcement on hundred percent voting Verdict on Voting Vote announcement on 51 voting on a single option 2 Web DPS SMS Gateway Intimate poll details Poll intimation Intimate Voting Result Result intimation 3 Web DPS Email server Intimate poll Details Poll intimation Intimate Voting Result Result intimation 4 SMS Gateway Web DPS Capture SMS Response Capture SMS vote 5 Email server Web DPS Capture Email Response Capture email vote 2 1 Web DPS standalone application DPS is a web based application that is developed using the Struts MVC Model II architecture The main aim of the MVC architecture is to separate the business logic and application data from the presentation data to the user Along with other benefits of this model unit testing for each tier presentation data and business is also easy to manage and to develop Moreover regressi
8. be used for DPS system implementation Table 6 1 Software Component List Sr no Software Component Product Suite Version 1 Jboss ESB jbossesb server 4 4 2 Apache Ant Apache 1 7 1 3 JDBC Listener jbossesb server 4 4 4 Email Listener jbossesb server 4 4 5 MySQL DB MySql 5 0 6 Email Server Winmail 4 6 T Eclipse platform Development IDE 3 3 1 1 8 Struts Apache Struts a flexible control 1 3 layer based for web programming 6 1 2 Web browsers client side DPS will be implemented so that it is fully functional in the following stable versions of the browsers Mozilla Firefox 1 5 or higher Internet Explorer 6 or higher 6 1 3 Mobile Handset Nokia N95 8GB Sony Ericsson z550i 6 1 4 Email Client Eudora 7 1 7 Responsibilities 7 1 Developers e To get the error reports from testers e To fix the missing functionalities in the application e To do initial testing of repaired application 7 2 User representative e To check if the application is fulfilling his her needs e Report any error bug encountered to tester 8 Test Deliverable Following section will depict the deliverables from testing of the product 8 1 Test Specifications Test specification defines the test cases used for the software testing Distributed Polling System Test Plan 9 n Wu M LARDALEN UNIVERSITY SWEDEN Table 8 1 Test specification FES
9. ceccuscssssscsesccceessasssocdsvcdctevessbeschadescsesvevesectacootesssev eees 6 4 TEST PASS FAIL GRITERIA E TE E E E E E E EEE E 7 5 VERIFICATION AND VALIDATION PROCESS csccsscsscccsccsccnccesccnccnsccnccescsccnccesscnscnsccncceccesccnccessonsonss 7 5 1 FEATURES TO BE TESTE Dinine o tak ae Re ATA rt iia 7 5 2 FEATURES NOT TO BE TESTEDaasass ssa ai kse ibarra dond tarada dla kaa dida dae elias ibid 7 5 3 TESTING APPROACH css 100 aais aasia sa daa saa aa KANNAN KS NN a SAR dessus ONT E Uu KA EKKS KUNA ASA KAAN dbasdanusaaisinaaheabandsteas LTA sdeasaaveaeyai 7 5 3 1 Requirements verification and Validation uosssosss oon aa aa aa a a ana an aan rra 8 6 TEST ENVIRONMENT auinaa aan sa saavaa sa vaava aon aoaNoTOa NS ANNA NTU TSN NO N aa NOU NSN NN VANNON n UN ive NSA NNN NA UN NNN NN NONN NNN NNNONNAN NNN ON ANNAN NMAVSTNENO 9 6 1 SOFTWARE sd citada N TUON TN aN RUSKEAAN T TN T N E TN ausuusanesuconabevasaghocpaassenvaeanacdeausanaeaveawadsueasied 9 6 1 1 A A A 9 6 1 2 Web browsers client side oocooncconoccnnoccnonccnonnnnnrncnanncnnnnonan ro aa eaa ana naa naa eaa ana eaa eaa aa aaasa 9 6 1 3 Mobile Handset cia M rs a deancacenadacacewagacccisesadenee viTMITKAITVNMTA NN 9 6 1 4 EMIT Clientes mannna a ta ideal cade tai 9 Te RESPONSIBILITIES lt i0snia ana ao asa sataa an sanaan taa Nanan ans ana den an NSN NN NNN SN KOON nan NN Ana ay NUO n KON Su KON NSTN NTS NL OKO NN NAN UNA Mn NNN N ON nn NSA NSUNUN
10. ent A suggestion for improvement that could be fixed any time 5 Verification and Validation Process Verification and Validation activities and tasks are defined throughout the development life cycle of DPS 5 1 Features to be tested The tests cover the functional reguirements of DPS as specified by the reguirements definition i e it is checked that the reguired functionality for executing all use cases is provided by the application 5 2 Features not to be tested Non functional reguirements such as scalability and few securities like HTTPS digital signature are not verified DPS uses features of the underlying frameworks Struts Tomcat JBoss for fulfilling these reguirements Jboss contains the security features built in so there is no need to develop and test these activities implicitly 5 3 Testing Approach High level approach for DPS testing activities are as follows 1 Finalization of test scenarios preparing test cases test data and script for automation if reguired 2 Components developed in each member s laptop needs to be tested by individual developer as per the output reguirement 3 Once the component is tested it needs to be dropped in the integration testing environment for Distributed Polling System Test Plan 7 ea Gy M LARDALEN UNIVERSITY Fee composition and make applications middleware ready for end to end testing Figure 5 1 4 For integration testing we will have to ensure that t
11. he interfaces required to trigger middleware interfaces are ready and tested during stand alone application testing 5 During simulation from middleware to test target applications availability of proper test data to synchronize target application configuration like manually configured email accounts middleware middleware com No Development of software components in Use this component eta launci to form the Application composition of all functioning components Form properly each application each developer s wo laptop EI 3 3 e syster 2 tanavior Beta Launch 9 adequate for j 2 si Figure 5 1 Test approach We will follow to adopt the following testing approaches for each development components 1 Sanity testing 2 Integration testing and then 3 bug fixing as depicted Figure 5 1 Test approach Sanity testing ensures that the component or the composed component is can be used for integration as a next step Integration testing ensures fulfilling functionality from end to end perspective Bug fixing arises at each step whenever there is found any bug at component development or during composition of components or during integration testing We believe that as soon as any bug is found in early phases of a DPS development life cycle it will reduce the effort and malfunctioning of the software 5 3 1 Requirements verification and validation Requirements testing ensure tha
12. ing portrayed are some of the critical success factors that will influence our testing of the stand alone application and the integrated product e Readiness of web DPS SMS Gateway and Email server applications by custom development and configurations e Test suite availability for integrating all the application through middleware Jboss e Completion of web DPS custom development to trigger Jboss integration interface e Resolution of connectivity establishment issue between middleware and the respective source target applications e Availability of test data e Availability support and collaboration of tester and developer to continue testing and bug fixing Distributed Polling System Test Plan 4 n M LARDALEN UNIVERSITY SWEDEN 2 Testing Scope o FES The document entails both stand alone application and integrated product testing plan Following are the applications involved in testing scope of DPS e Web DPS e Email server e SMS Gateway We will be testing web DPS custom built application in detail as it will be providing major functionalities from end user perspective Whereas Email server and SMS Gateway will be used as subsidiary application to facilitate the system functionality to send receive SMS to from end user s mobile device and sending receiving email to from configured email recipients as attachment and so on Table 2 1 Features to be tested S No Source System Target System Process N
13. lure Conditions Please refer to DPS Frror Handling Document 4 Test Pass Fail Criteria This section specifies the pass fail criteria definition that will denote whether a test case has passed or failed the testing gualification once it is executed A test case will be considered passed if it meets the following criteria e The test case meets the output requirement once executed as defined by the requirement and design e Allreguired steps should be executed for the particular test case e Noabnormal behavior pops up during execution of the test case A test case will be considered failed if it meets any of the following criteria e Allreguired steps are not executed during test case execution e Does not meet output reguirements e Any side effect or abnormal behavior pops up during execution For failed test cases there will be logging mechanism to log the failed test case as defect in software For defect also there will be different level of severity definition as portrayed in below table Table 5 1 Severity Level Severity Level Description Most Critical It specifies an urgent call needs to be taken on the issue high level management intervention reguired further steps can not be proceeded Major Same as above but here a work around is available and fix could be provided Medium A defect that needs to be fixed as soon as possible prior to deployment Minor A defect and needs to be looked into Enhancem
14. on testing is also not a big deal to apply on a system for testing the rest of the application in case of any system update In Figure 2 1 Struts Request processing flow DPS user request flow using this model is depicted Distributed Polling System Test Plan 5 v FER Struts Flow Diagram web xml container config Serviet mappings Controller Business Objects Usable from Controller View amp Model Model Keeps State Strut Tag Libraries Resource Properties File Figure 2 1 Struts Request processing flow DPS is a web based application designed and developed using the MVC pattern Thus it consists mainly three tiers Web tier Business tier Database tier 2 1 1 Web tier testing In a typical enterprise application many areas require testing Starting from the simplest component classes the developers or specialized test developers need to program unit tests to ensure that the application s smallest units behave correctly 2 1 2 Database and business tier testing During the development phase of DPS we have used the Test Driven Development approach So before going for the actual implementation we have first designed and developed the unit test cases and then we have written the code actual implementation that passes the designed unit test cases 3 Test Entry Exit criteria This section specifies the entry and exit criteria for DPS testing It specifies general
15. t the requirements have been interpreted correctly are reasonable and are recorded properly In software industry different approaches are being used for requirement verification and validation like prototyping tracing approaches user manual writing reviews and inspections We used the Review approach for requirement verification and validation In regards of this approach we read and analyze the requirements from the SCORE document then conduct internal team meetings discuss the problems and agreed on actions to address these problems Meanwhile we also arranged meetings with internal customer i e project supervisors to validate the requirements As an external customer was not involved on site during development span but he was involved through electronic means of communication For requirement validation we clarify requirements from the external customer through emails and he gave us feed back with some changes and finally after the changes were made it was verified and validated by internal customer Finally we were able to put requirement analysis to next level of development phase Distributed Polling System Test Plan 8 n M LARDALEN UNIVERSITY SWEDEN 6 Test Environment 6 1 Software 6 1 1 Base technologies Due to versatile nature of the architecture scalability and for loose coupling design a lot of software components need to interact with each other Following is the list of software components to

Download Pdf Manuals

image

Related Search

Related Contents

Mode d`emploi Dimmax 4-950 Proline  Especificações e Características de Motor  Xerox Color Laser Printer User's Manual    DURO ROCK. S.A. de C.V.  QuaPro-R 0.9-1.8カタログ (PDFファイル:2968KB)  MODEL 2500 & 1500 - Donamarc Water Systems Co.  

Copyright © All rights reserved.
DMCA: DMCA_mwitty#outlook.com.