Web Testing of an e-governance Application A Case Study

Transcription

1 Web Testing of an e-governance Application A Case Study Sanjay G Kulkarni, Scientist D National Informatics Centre, Ganeshkhind Road, Pune kulkarni.sg@nic.in Abstract-The software testing done for a web application software is called web testing. An e-governance web application Sarathi module has been developed for all State Governments working under of Ministry of Road and Transport Government of India. The testing before still to be launch product was done for Maharashtra, involving the RTO office staff of the different parts of Maharashtra. The testing involved user creations, workflow testing, navigation testing, setting of the parameters, Testing,e- payment gateway testing, creation of masters, customization testing etc. The Sarathi Module deals with the issuing of the License to the applicant and various processes involved in making this as a usable e-governance product across the country. This requires customization for each states, with the different procedures and processes involved. This paper gives overview of the web testing done for the State of Maharashtra as the product is not released all product related the information of the testing are not given in the paper. Keywords : e-governance, web testing, RTO and rules in this regard need to be amended for the benefit of the citizen. Sarathi-on-Web facilitates public to submit applications for Learning & Driving License related transactions thru this mode. The application data is in turn transferred to the remote RTO/DTOs of the states for further processing of the request (submitted thru ONLINE) at the local RTO/DTO Office. Services like E-payment Gate Way, Common Service Centre, SSDG and Service partners are also being provide I. INTRODUCTION The Information and communication technology has changed the way of working, it may be any organisation Government or private. In today s world existence of the Government department is known if it is on the Internet. The business of the Government now focus is on the citizen centric application, providing the government services to the citizens at a cost effective way as well as efficiently. This is possible when all the department workflows are automated, rules amended, legislations passed if required and doing business process engineering taking into account with the latest IT Act of the country. Simplifying procedures how the Government works cutting down the levels to ease working and uniformity of the Business rules across the country. To give an example in transport if the Citizen wants to renew his Driving Licence he should be able to do it going to any RTO office of the country. It means the record has to be available to the RTO renewing the Licence and it could be the electronic record II. E-GOVERNANCE Electronic governance or e-governance is the application of ICT for delivering the Government Services, electronic exchange of information having the transaction possible over the Net. The model could be one of the many models Government to Government(G2G), Government to Customer(G2C), Government to Employee(G2E) etc. III. UNDERSTANDING ORGANISATION S WORKING Before going for testing it is necessary to understand the working of the organization.there are around 50 RTO s for which this module is to be implemented. The chart of the organistion for State of Maharashtra is given in the chart -1 34

2 Transport Commissioner. RTO -1 RTO -2 RTO-50 Chart 1 Showing the Organisation Structure of Transport Department. There is one State coordination or State user who defines the rules and procedures in the system (State Masters) and all the regional offices under the transport department follow the same rules and procedures defined by the State User. He creates the users for the RTOs and the RTO user creates the staff users who are given the responsibility of that window or counter. This is the logical user workflow of the system for the user management. IV. SYSTEM ARCHITECTURE The cloud architecture will be used for the application with the required configuration, is shown in the Diagram 1 Application Server, Web server, Data base Server etc Payment Services Services Public RTO Department Figure-2 Showing the System Architecture of the RTO Application 35

3 V. WEB TESTING A web based application software is accessed over the Internet. Any web based application for beta testing requires to be tested with the user as he has domain knowledge and he is involved in the day to day operational work of the department. VI. E_GOVERNANCE WEBSITE An e_governance Site of RTO or any other department has two important purposes to be looked into 1) The Information dissemination It could be schemes, rules, various forms template, FAQs, Vision of the Department etc 2) The application software for the delivering of the service to be public and to the Department.Which could be online entry of the application, further alerts by SMS to the applicant, viewing the status of the application, online booking of the test slot etc and for the department scrutiny, approval till the giving of the License/permit and the maintenance of the record for official purpose. The beta testing involved in looking into the documents eg the user manual, rules and procedures followed by the department and creation of the test plan. Then setting of the test environment, identification of the manpower, hardware resources, setting of the browser for testing. VII. RISK MITIGATION AND STRATEGY A risk mitigation plan and strategy was made to mention few of them are given in the table -1. Sr. Risk Factor Severity Likelihood Risk Mitigation No. 1. Provision of Test Environment High Medium Check for presence of PCs offering all the hardware and software needed for testing 2. Suspension of testing due to detection of major failure High Likely Initial care will be taken on project development, 3. Availability of manpower for testing / support/ correction 6. Availability of manpower for support/ correction finding any pitfalls sooner High Likely Identification of the staff for testing has been done and responsibility for job completion is entrusted by Department for user side. High Likely Identification of the staff for support /correction has been done and responsibility for job completion is entrusted by Transport Department for user side. TABLE -1 RISK IDENTIFICATION AND MITIGATION 36

4 VIII. MATRIX OF LIST OF FEATURES TO BE TESTED The matrix of the features to be tested was made as per the test plan and the checklist was made to comply with the features to be tested Also scope was decided in the Test Plan. IX. TEST APPROACH The approach was taken for the testing of the application software which was manual testing A. Functional Testing The application is behaving in terms of the functionality desired. It could be business work flows, navigation, Links working properly (eg. The url is not showing the site which is desired.) etc. B. Browser Compatibility The application should work with all the different browsers of latest versions. The Application Should display the same result on the screen and needs to be tested by invoking the url in the different browser. C. Usability All the e-governance should comply with the Government of India Guidelines which are for the design,accessibility aspects etc. There should be same look and feel for all the pages and ease of use for disabled person also. D. Security This is very important aspect which needs to be checked for the application. There are about 5000 attacks on e-governance Website and all the measures are required to be taken for protecting the Government Data. It involves filtering of the user inputs, non entry of the reserved words, blocking scripts running etc. The authorised user is required to be able to access which is two level authentication, pin entry received on mobile etc. E. Performance Testing Performance testing such as stress test, load test etc was not done for this application by the testing team which was out of scope of the test plan. F. Interface testing An web application consists of the database, webserver, Application server and it is required to test these interfaces are working properly without any leakages. X. TESTING TASKS, RESPONSIBILITIES AND SCHEDULE The task of testing was distributed with the roles and responsibility and with the schedule as mentioned in the Table -2 Sr. No. Task Responsibility Completion Date 1. Prepare Test PL Plan 2. Prepare Test Cases PL / Developer / User 3. Execute tests User / Developer 4. Prepare Test PL/User Reports 5. Retesting User / Developer TABLE -2 TESTING TASKS, RESPONSIBILITIES AND SCHEDULE XI. PASS / FALL CRITERIA Testing will deemed to be completed if All planned tests have been executed All identified defects have been removed. 37

5 XII. SUSPENSION CRITERIA AND RESUMPTION REQUIREMENTS A. Suspension requirements include : Defects found which seriously impact test progress Test environment not available at time of test schedule Assigned test resources not available B. Resumption requirements include : Resumption of testing only after the problem has been resolved. XIII. TEST DELIVERABLES Test Plan Test Data Test Cases and results Test Summary XIV. CONCLUSION This paper has covered various aspects of the web testing of a real life e-governance application. It involves the customisation of the product, building of the testing team, the time and schedule management, risk mitigation plan and timely deliverables expected and various aspects related to it. The difference between a commercial site and the e-governance site is the e-governance site has to adopt the e-governance standards defined for the delivery of the services in cost effective way. REFERENCES [1] Ministry of Road and Transport GoM [2] M.V. Act Government of India 1988 [3] Sarathi on Web (website) [4] Test Plan Tribe Certificate Verification Information System 38