Web Engineering: A Practitioner Approach Chapter 15:Testing WebApps Testing Concepts Content Testing User Interface Testing Usability Testing Compatibility Testing Component-Level Testing Navigation Testing Configuration Testing Security and Performance Testing Chapter 16 :Change And Content Management Change Change Management for Web Engineering Content Management Criteria for Implementing a Content Management System (CMS)

1. 5/13/2018 1
Web Engineering: A Practitioner Approach , by Roger S. Pressman and
David Lowe
Presented by: Esraa A. Farrag
Presented to : Prof.Dr. Shereen Mousa

2. 5/13/2018 2
• Testing WebApps
1 •Testing Concepts
2 •Content Testing
3 •User Interface Testing
4 •Usability Testing
5 •Compatibility Testing
6 •Component-Level Testing
7 •Navigation Testing
8 •Configuration Testing
9 •Security and Performance Testing
• Change And Content Management
10 •Change
11 •Change Management for Web Engineering
12 •Content Management
13 •Criteria for Implementing a CMS

3. Testing WebApps
5/13/2018 3

4. Testing Concepts
5/13/2018 4

5. Testing Concepts
Testing is the process of exercising a WebApp with the intent of finding (and ultimately
correcting) errors.
Tests must be designed to uncover errors in WebApps that are implemented in:
◦ different operating systems
◦ browsers [or other interface devices such as set-top boxes, personal digital assistants
(PDAs), and mobile phones]
◦ hardware platforms
◦ communications protocols
5/13/2018 5

6. Dimensions of Quality
Content
Function
Structure
Usability
Navigability
Performance
Compatibility
Interoperability
Security
5/13/2018 6

7. Dimensions of Quality
• Content is evaluated at both a syntactic and semantic level. At the syntactic level, spelling, punctuation, and
grammar are assessed for text-based documents. At a semantic level, correctness (of information presented),
consistency (across the entire content object and related objects), and lack of ambiguity are all assessed.
• Function is tested to uncover errors that indicate lack of conformance to stakeholder requirements. Each WebApp
function is assessed for correctness, instability, and general conformance to appropriate implementation standards
(e.g., Java or XML language standards).
• Structure is assessed to ensure that it properly delivers WebApp content and function, is extensible, and can be
supported as new content or functionality is added.
• Usability is tested to ensure that each category of user is supported by the interface and can learn and apply all
required navigation syntax and semantics.
• Navigability is tested to ensure that all navigation syntax and semantics are exercised to uncover any navigation
errors (e.g., dead links, improper links, erroneous links).
5/13/2018 7

8. Dimensions of Quality
• Performance is tested under a variety of operating conditions, configurations, and loading to ensure that the
system is responsive to user interaction and handles extreme loading without unacceptable operational
degradation.
• Compatibility is tested by executing the WebApp in a variety of different host configurations on both the
client and server sides. The intent is to find errors that are specific to a unique host configuration.
• Interoperability is tested to ensure that the WebApp properly interfaces with other applications and/or
databases
• Security is tested by assessing potential vulnerabilities and attempting to exploit each. Any successful
penetration attempt is deemed a security failure.
5/13/2018 8

9. 5/13/2018 9
The testing process

10. Content Testing
5/13/2018 10

11. Content Testing
 Content testing combines both reviews and the generation of executable test cases.
 Reviews are applied to uncover semantic errors in content.
 Executable testing is used to uncover content errors that can be traced to dynamically derived content that is
driven by data acquired from one or more databases.
 Content testing has three important objectives:
 to uncover syntactic errors (e.g., typos, grammar mistakes) in text-based documents, graphical representations,
and other media,
 to uncover semantic errors (i.e., errors in the accuracy or completeness of information) in any content object
presented as navigation occurs, and
 to find errors in the organization or structure of content that is presented to the end user.
5/13/2018 11

12. 5/13/2018 12
Database Testing

13. User Interface Testing
5/13/2018 13

14. 5/13/2018 14
Client-side
pop-up
windows
User Interface – Testing specific elements

15. Usability Testing
5/13/2018 15

16. Usability Testing
Similar to interface semantics testing in the sense that it evaluates:
◦ the degree to which users can interact effectively with the WebApp
◦ the degree to which the WebApp guides users’ actions, provides meaningful feedback and
enforces a consistent interaction approach.
Determines the degree to which the WebApp interface makes the user’s life easy
5/13/2018 16

17. Usability Test Categories
Interactivity.
•Are interaction mechanisms (e.g., pull-down menus, buttons, pointers) easy to understand and use?
Layout.
• Are navigation mechanisms, content, and functions placed in a manner that allows the user to find them quickly?
Readability.
•Is text well written and understandable? Are graphic representations intuitive and easy to understand?
Aesthetics.
• Do the layout, color, typeface, and related characteristics lead to ease of use? Do users “feel comfortable” with the look and feel of the WebApp?
Display characteristics.
• Does the WebApp make optimal use of screen size and resolution?
Time sensitivity.
• Can important features, functions, and content be used or acquired in a timely manner?
Personalization.
• Does the WebApp appropriately tailor itself to the specific needs of different user categories or individual users?
5/13/2018 17

18. Qualitative Assessment of Usability
5/13/2018 18

19. Compatibility Testing
5/13/2018 19

20. Compatibility Testing
WebApps operate in complex (and often unpredictable) environments
◦ Different browsers, screen resolutions, operating systems, plug-ins, access bandwidths, etc.
Serious errors can be caused by obscure combinations
Most common problem is deterioration in usability:
◦ Download speeds may become unacceptable
◦ Missing plug-ins may make content unavailable
◦ Browser differences can change page layout or legibility
◦ Forms may be improperly organized.
Compatibility testing strives to uncover these problems before the WebApp
goes online.
◦ First step is to define a set of “commonly encountered” client-side configurations and their
variants.
◦ Next, derive a series of compatibility validation tests (from existing interface tests, navigation
tests, performance tests, and security tests).
5/13/2018 20

21. Component-Level Testing
5/13/2018 21

22. Component-Level Testing
Component-level testing, also called function testing, focuses on a set of tests that attempt
to uncover errors in WebApp functions
Applies the following test-case design methods:
◦ Equivalence partitioning
◦ Boundary value analysis
◦ Path testing
5/13/2018 22

23. Selecting Components to Test
◦ Which functionality in the Web site is most critical to its purpose?
◦ Which areas of the site require the heaviest database interaction?
◦ Which aspects of the site’s CGI, applets, ActiveX components, and so on
are most complex?
◦ What types of problems would cause the most complaints or the worst
publicity?
◦ What areas of the site will be the most popular?
◦ What aspects of the site have the highest security risks?
5/13/2018 23

24. Navigation Testing
5/13/2018 24

25. Each of the following navigation mechanisms should be tested
5/13/2018 25
navigation
mechanisms
Navigation
links.
Redirects.
Bookmarks.
Frames and
framesets.
Site maps.
Internal
search
engines.

26. Navigation Semantics
As navigation design is conducted, you create “a set of information and
related navigation structures that collaborate in the fulfillment of a subset of
related user requirements” [Cac02].
These are sometimes referred to as navigation semantic units (NSUs) and
are defined by a set of navigation paths (called “ways of navigating”) that
connect navigation nodes (e.g., Web pages, content objects, or
functionality).
Taken as a whole, each NSU allows a user to achieve specific requirements
defined by one or more use cases for a user category.
Navigation testing exercises each NSU to ensure that these requirements
can be achieved.
5/13/2018 26

27. Configuration Testing
5/13/2018 27

28. Configuration Testing
Configuration variability and instability are important factors that make Web engineering a
challenge.
◦ Hardware, operating system(s), browsers, storage capacity, network communication speeds, and a variety of other client-side
factors are difficult to predict for each user.
The job of configuration testing is to test a set of probable client-side and server-side
configurations to ensure that the user experience will be the same on all of them and to
isolate errors that may be specific to a particular configuration.
5/13/2018 28

29. Testing Strategy
 Server-side. configuration test cases are designed to verify that the projected server configuration
[i.e., WebApp server, database server, operating system(s), firewall software, concurrent
applications] can support the WebApp without error.
 Client-side. On the client side, configuration tests focus more heavily on WebApp compatibility with
configurations that contain one or more permutations of the following components:
 Hardware. CPU, memory, storage, and printing devices
 Operating systems. Linux, Macintosh OS, Microsoft Windows, a mobile-based OS
 Browser software. FireFox, Internet Explorer, Safari, Mozilla/Netscape, Opera, and others
 User interface components. Active X, Java applets, and others
 Plug-ins. QuickTime, RealPlayer, and many others
 Connectivity. Cable, DSL, regular modem, industry-grade connectivity (e.g., T1 lines)
5/13/2018 29

30. Security and Performance Testing
5/13/2018 30

31. Security and Performance Testing
 Security and performance testing address the three distinct elements of the WebApp
infrastructure
 the server-side environment that provides the gateway to Internet users
 the network communication pathway between the server and the client machine
 the client-side environment that provides the end user with a direct interface to the WebApp.
 Security testing focuses on unauthorized access to WebApp content and functionality
along with other systems that cooperate with the WebApp on the server side.
 Performance testing focuses on the operating characteristics of the WebApp and on
whether those operating characteristics meet the needs of end users.
5/13/2018 31

32. Security
Testing
Firewalls
Authentication
Encryption
Authorization
5/13/2018 32

33. Performance Testing
 Objectives:
• Does the server response time degrade to a point where it is noticeable and unacceptable?
• At what point (in terms of users, transactions, or data loading) does performance become unacceptable?
• What system components are responsible for performance degradation?
• What is the average response time for users under a variety of loading conditions?
• Does performance degradation have an impact on system security?
• Is WebApp reliability or accuracy affected as the load on the system grows?
• What happens when loads that are greater than maximum server capacity are applied?
• What is the impact of poor performance on company revenues?
 Load testing determines how the WebApp and its server-side environment will respond to various
loading conditions.
 Stress testing is a continuation of load testing, but in this instance the variables, N, T, and D are
forced to meet and then exceed operational limits.
5/13/2018 33

34. Change And Content
Management
5/13/2018 34

35. Change
5/13/2018 35

36. Change management procedures and a content management system work in conjunction with one
another to help ensure that
◦ all requested changes to WebApp content and functionality are managed in a way that does not disrupt the
Web engineering process or corrupt the quality of the WebApp itself, and
◦ all WebApp content is properly collected, structured, and presented to the end user who requests it.
Change management: ensures that changes are made correctly, recorded for future reference, and
do not conflict with other changes that have already been made.
Content management: collects, manages, and publishes all content that is seen by each end-user
category, including content (and functions) that have undergone change.
5/13/2018 36

37. Attributes of
a “Change”
Description
Impact
Target
Implementation
pathway
History
Explains the nature of the
change from the point of view
of the stakeholder(s) affected
by the change
describes the technical aspects of
how the change will be made
defines the specific WebApp
objects (both content and
functionality) that will be changed
describes how the change will
manifest itself externally (what
end users will see) and how it will
affect the internal content and
functionality of the WebApp
records when the change was
requested, assessed, and
implemented and what WebApp
content and functionality was
affected
5/13/2018 37

38. Elements of the WebApp
Change
5/13/2018 38

39. Change Management for Web
Engineering
5/13/2018 39

40. Change Control
Class 1
• A content or function change that corrects an error or enhances local content or functionality
Class 2
• A content or function change that has an impact on other content objects or functional components within the
increment
Class 3
• A content or function change that has a broad impact across a WebApp
(e.g., major extension of functionality, significant enhancement or reduction in content, major required changes
in navigation)
Class 4
• A major design change (e.g., a change in interface design or navigation approach) that will be immediately
noticeable to one or more categories of end users
5/13/2018 40

41. Figure 1 :Managing changes for WebApps.5/13/2018 41

42. Content Management
5/13/2018 42

43. Content Management
content management is about gaining control over the creation and distribution of
information and functionality.
5/13/2018 43

44. What Are the Major Elements of a
Content Management Systems (CMS)?
Content
Management
System
The
management
subsystem
Content
database.
Database
capabilities
Change
management
functions
The
collection
subsystem
The
publishing
subsystem
Static
elements
Publication
services
External
services
5/13/2018 44

45. Figure 2 :Content management system
5/13/2018 45

46. 5/13/2018 46

47. The collection subsystem
The collection subsystem encompasses all actions required to create
and/or acquire content, and the technical functions that are necessary to
convert content into a form that can be represented by a markup
language (e.g., HTML, XML) and to organize Content Into Packets That
Can Be Displayed Effectively on the Client side.
5/13/2018 47

48. 5/13/2018 48

49. The publishing subsystem
Content must be extracted from the repository, converted to a form that is suitable for
publication, and formatted so that it can be transmitted to client-side browsers.
The publishing subsystem usually accomplishes these tasks using a series of templates. Each
template is a function that builds a publication using one of three different components:
• Static elements. Text, graphics, media, and scripts that require no further processing are
transmitted directly to the client side.
• Publication services. Provide function calls to specific retrieval and formatting services that
personalize content ,perform data conversion, and build appropriate navigation links.
• External services. Provide access to external corporate information infrastructure such as third
party web services.
5/13/2018 49

50. Figure 3 :CMS repository
5/13/2018 50

51. Criteria for Implementing a CMS
5/13/2018 51

52. Criteria for Implementing a CMS
Criteria for
Implementing a
CMS
Publication
volume
Change
volume
Contributor
population
Content
volume
5/13/2018 52

53. References
- Web Engineering: A Practitioner Approach , by Roger S. Pressman and David Lowe
5/13/2018 53

54. 5/13/2018 54

55. 5/13/2018 55