Chapter 5 - Testing the Web Application

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/31

flashcard set

Earn XP

Description and Tags

32 Terms

1
New cards

Website Quality Attributes

1) Timeliness, 2) Structural quality, 3) Content/relevance, 4) Accuracy & consistency, 5) Response time & latency, 6) Performance.

2
New cards

Structural Quality (Web)

Ensuring all structural parts work properly, such as all internal/external links functioning and all images loading without defect.

3
New cards

Response Time & Latency in Web Testing

The speed of server response after a user action (e.g. clicking Submit), crucial for preventing user abandonment on e-commerce sites.

4
New cards

Web Application Challenges

Short release cycles, rapidly changing technology, massive user surges at launch, inability to control user client environments, and 24/7 availability.

5
New cards

Proxy Server (Role in Web Architecture)

Software acting as the sole connection between a private network and the internet; caches data to improve performance and filters files.

6
New cards

Firewall (Definition & Role)

A combination of hardware and software that examines incoming packets to ensure legitimate sources and block unauthorized intrusion.

7
New cards

Static Verification in Web Testing

Scanning HTML source pages without execution to detect navigation faults, data flow issues, unreachable pages, or ghost pages.

8
New cards

Unreachable Pages

Web pages that exist on the server but cannot be reached along any navigation path starting from the initial home page.

9
New cards

Ghost Pages

Pages referenced by pending or broken links that do not actually exist on the server.

10
New cards

Dynamic Validation (White-Box Web Testing)

Assessing web internal structure to measure test coverage; test cases consist of sequences of visited URLs and form inputs.

11
New cards

Page Testing vs. Hyperlink Testing

Page testing requires every page to be visited at least once; Hyperlink testing requires every hyperlink to be traversed at least once.

12
New cards

Functional Web Testing

Verifies interactive features (forms, searches, popups, shopping carts, payments) and dynamically generated pages created from database queries.

13
New cards

Database Testing Key Issues

1) Data integrity, 2) Data validity, 3) Query translation (user request to SQL), 4) Data manipulation/updates (e.g. stock counts).

14
New cards

Testable Web UI Mechanisms

Links, forms, client-side scripts, dynamic HTML, pop-up windows, streaming content, and cookies.

15
New cards

Cookie Testing Aspects

Ensuring correct construction, accurate transmission, appropriate persistence level, and proper attachment by the web application.

16
New cards

Usability Testing (Core Principle & Steps)

Studying what users actually do; involves defining categories/goals, designing tests, selecting participants, instrumenting interactions, and assessing usability.

17
New cards

Compatibility Testing (Web)

Testing website layout, objects, fonts, colors, and client scripts across multiple web browsers, OS platforms, and monitor resolutions.

18
New cards

Navigation Testing (Syntactic)

Testing mechanisms like internal/external links, redirects (broken/changed URLs), bookmarks (title extraction), frames, site maps, and internal search engines.

19
New cards

Navigation Semantic Unit (NSU)

A set of navigation paths connecting navigation nodes that allows a specific user category to achieve a use-case goal.

20
New cards

Forms Testing Actions

Checking field tab order (forward/backward), testing boundary values, trapping invalid data (dates/numbers), and verifying correct database updates.

21
New cards

Configuration Testing (Server vs. Client)

Server-side tests OS compatibility, directory creation, scripts, and DB integration; Client-side tests user hardware, OS, browsers, plug-ins, and connection speeds.

22
New cards

Security Testing: 4 Core Elements

1) Firewalls, 2) Authentication, 3) Encryption, 4) Authorization.

23
New cards

Authentication vs. Authorization

Authentication validates identity (who you are); Authorization filters access based on permissions/credentials (what you are allowed to access).

24
New cards

Encryption & Digital Certificates

Encoding sensitive data to make it unreadable to attackers; digital certificates allow clients to verify the authenticity of the destination.

25
New cards

Scalability (Definition)

The web application's capacity to sustain a high number of concurrent users/transactions while maintaining acceptable response times.

26
New cards

Load Testing

Simulating expected real-world usage by generating many simultaneous users/requests to evaluate performance under normal to heavy traffic.

27
New cards

Stress Testing

Subjecting the system to varying and extreme/beyond-capacity loads for extended periods to evaluate breaking points, CPU/memory limits, and degradation.

28
New cards

End-to-End Transaction Testing

Testing the complete customer workflow from site arrival to exit across all tiers (browser, web/app server, DB, middleware).

29
New cards

Post-Implementation Testing

Testing performed in the actual production environment after deployment to verify live behavior.

30
New cards

Post-Implementation Strategy Components

1) Timeline of events, 2) Team identification chart, 3) Acceptance test checklist, 4) Load test checklist/scripts, 5) Rollback plan.

31
New cards

Rollback Plan (Post-Implementation)

A contingency procedure to cleanly restore the production environment to its original state if a deployment fails, followed by acceptance tests.

32
New cards