Issues such as the security of the web application, the basic functionality of the site, its accessibility to handicapped users and fully able users, as well as readiness for expected traffic and number of users and the ability to survive a massive spike in user traffic, both of which are related to load testing.
Issues such as the security of the web application, the basic functionality of the site, its accessibility to handicapped users and fully able users, as well as readiness for expected traffic and number of users and the ability to survive a massive spike in user traffic, both of which are related to load testing.
Issues such as the security of the web application, the basic functionality of the site, its accessibility to handicapped users and fully able users, as well as readiness for expected traffic and number of users and the ability to survive a massive spike in user traffic, both of which are related to load testing.
Live projects Assessing Web Quality Content evaluated at both syntactic and semantic levels Function tested to uncover lack of conformance to requirements Structure is assessed to ensure proper content and function are delivered Usability is tested to ensure that each category of user can be supported as new content or functionality is added Assessing Web Quality Navigability is tested to ensure that all navigation syntax and semantics are exercised erformance is tested under a variety of operating conditions! configurations! and loading to ensure a reasonable level of user response Compatibility tested by executing "eb#pp using a variety of client and server configurations Assessing Web Quality $nteroperability tested to ensure proper interfaces to other applications and databases Security is tested by assessing potential vulnerabilities and trying to exploit each of them Web Error Concerns -1 %any types of "eb#pp tests uncover problems evidenced on the client side using an specific interface &e'g' may be an error symptom! not the error itself( $t may be difficult to reproduce errors outside of the environment in which the error was originally encountered %any errors can be traced to the "eb#pp configuration! incorrect design! or improper )*%+ Web Error Concerns - $t is hard to determine whether errors are caused by problems with the server! the client! or the network itself Some errors are attributable to problems in the static operating environment and some are attributable to the dynamic operating environment !esting Web Apps - 1 "eb#pp content model is reviewed to uncover errors' $nterface model is reviewed to ensure all use,cases are accommodated' -esign model for "eb#pp is reviewed to uncover navigation errors' User interface is tested to uncover presentation errors and.or navigation mechanics problems' !esting Web Apps - Selected functional components are unit tested' Navigation throughout the architecture is tested' "eb#pp is implemented in a variety of different environmental configurations and the compatibility of "eb#pp with each is assessed' Security tests are conducted' !esting Web Apps - " erformance tests are conducted' "eb#pp is tested by a monitored group of selected end,users looking for / content errors / navigation errors / usability concerns / compatibility issues / performance Web App !esting #rocess - 1 Content testing / tries to uncover content errors $nterface testing / exercises interaction mechanisms and validates aesthetic aspects of U$ Navigation testing / use,cases basis for design of test cases that exercise each usage scenarios against the navigation design &integration testing( Web App !esting #rocess - Component testing / exercises the "eb#pp content and functional units &integration testing( Configuration testing / attempts to uncover errors traceable to a specific client or server environment / cross,reference table is useful Web App !esting #rocess - " erformance testing to assess / "eb#pp response time and reliability under varying system loads / "hich "eb#pp components are responsible for system degradation / )ow performance degradation impacts overall "eb#pp requirements Security testing / tests designed to exploit "eb#pp or environment vulnerabilities Web !esting !ask $et - 1 0eview stakeholder requirements 1stablish priorities to ensure each user goal will be adequately tested -efine "eb#pp testing strategy by describing the types of tests that will be conducted Web !esting !ask $et - -evelop test plan / -efine test schedule and assign testing responsibilities / Specify automated testing tools / -efine acceptance criteria for each class of test / Specify defect tracking mechanisms / -efine problem reporting mechanisms Web !esting !ask $et - " erform unit tests / 0eview content for syntax and semantics errors / 0eview content for proper permissions / *est operation of interface mechanisms / *est each component for proper function Web !esting !ask $et - % erform integration tests / *est interface semantics against use, cases / Conduct navigation tests erform configuration tests / #ssess client,side compatibility / #ssess server,side configurations Conduct performance tests Conduct security tests Content !esting Objectives Uncover syntactic errors in all media / &e'g' typos( Uncover semantic errors / &e'g' errors in completeness or accuracy( Find errors in organi2ation or structure of content presented to end,user &atabase !esting - 1 *he original query must be checked to uncover errors in translating the user3s request to S4+ roblems in communicating between the "eb#pp server and -atabase server need to be tested' &atabase !esting - Need to demonstrate the validity of the raw data sent from the database to the "eb#pp and the validity of the transformations applied to the raw data' Need to test validity of dynamic content ob5ect formats transmitted to the user and the validity of the transformations to make the data visible to the user' 'ser (nter)ace !esting - 1 $nterface features are tested to ensure that design rules! aesthetics! and related visual content is available for user without error' $ndividual interface mechanisms are tested using unit testing strategies' 1ach interface mechanism is tested in the context of a use,case of navigation semantic unit &e'g' thread( for a specific user category 'ser (nter)ace !esting - Complete interface is tested against selected use,cases and navigation semantic unit to uncover interface semantic errors $nterface is tested in a variety of environments to ensure compatibility !estable Web *echanis+s - 1 +inks / each link is listed and tested Forms / check labels! field navigation! data entry! error checking! data transmission! meaningful error messages Client,side scripting / black box testing and compatibility tests !estable Web *echanis+s - -ynamic )*%+ / correctness of generated )*%+ / compatibility tests Client,side pop,up windows / proper si2e and placement of pop,up / working controls / consistent with appearance of "eb page Streaming content &demonstrate existence! accuracy! and control over content display( !estable Web *echanis+s - " Streaming content &demonstrate existence! accuracy! and control over content display( Cookies / check that server constructs cookie correctly / cookie transmitted correctly / ensure proper level of persistence / check to see "eb#pp attaches the correct cookies #pplication specific interface mechanisms 'sability !esting Goals - 1 $nteractivity / interaction mechanisms are easy to understand and use +ayout / navigation! content! and functions allows user to find them quickly 0eadability / content understandable #esthetics / graphic design supports easy of use 'sability !esting Goals - 1 -isplay characteristics / "eb#pp makes good use of screen si2e and resolution *ime sensitivity / content and features can be acquired in timely manner ersonali2ation / adaptive interfaces #ccessibility / special needs users 'sability !esting -efine set of usability testing categories and identify goals for each -esign tests the will enable each goal to be evaluated Select participants to conduct the tests $nstrument participants3 interactions with the "eb#pp during testing -evelop method for assessing usability of the "eb#pp Co+patibility !esting 6oal is to uncover execution problems that can be traced to configuration differences / -efine a set of commonly encountered client,side computing configurations and their variants / 7rgani2e this information &computing platform! typical display devices! operating system! available browsers! connection speeds( / -erive compatibility validation test suite from existing interface tests! navigation tests! performance tests! and security tests Co+ponent Level !esting 8lack box and white box testing of each "eb#pp function Useful test case design methods / 1quivalence partitioning / 8oundary value analysis &esp' form field values( / ath testing / Forced error testing $yntactic ,avigation !esting +inks 0edirects 8ookmarks Frames and framesets Site maps $nternal search engines $e+antic ,avigation !esting Navigation semantic units are defined by a set of pathways that connect navigation nodes 1ach NSU must allows a user from a defined user category achieve specific requirements defined by a use,case *esting needs to ensure that each path is executed in its entity without error 1very relevant path must be tested User must be given guidance to follow or discontinue each path based on current location in site map Con)iguration !esting $erver-$i-e Compatibility of "eb#pp with server 7S Correct file and directory creation by "eb#pp System security measures do not degrade user service by "eb#pp *esting "eb#pp with distributed server configuration "eb#pp properly integrated with database software Correct execution of "eb#pp scripts 1xamination system administration errors for impact on "eb#pp 7n,site testing of proxy servers Con)iguration !esting Client-$i-e )ardware 7perating systems 8rowser software User interface components lug,ins Connectivity !estable $ecurity Ele+ents Firewalls #uthentication 1ncryption #uthori2ation Loa- !esting -etermine combinations of N! *! and - that cause performance to degrade N 9 number of concurrent users * 9 number of on,line transactions per unit of time - 9 data load processed by server per transaction 7verall through put is computed using the equation 9 N : * : - $tress !esting -oes system degrade gracefully; #re users made aware that they cannot reach the server; -oes server queue resource requests during heavy demand and then process the queue when demand lessens; #re transactions lost as capacity is exceeded; $s data integrity affected when capacity is exceeded; )ow long till system comes back on,line after a failure; #re certain "eb#pp functions discontinued as capacity is reached;