Web Application Testing: How to Test a Website? Types
ๆ้ฉฌๆฏยทๆฑๅฏๅฐ้กฟ
โก ๆบ่ฝๆ่ฆ
Web Application Testing verifies a website across functionality, usability, interface, database, compatibility, performance, security, and crowd checks before release, so defects surface in staging rather than in front of paying users.
Before we pen down more details on the types of web testing, let us quickly define web testing and see where it fits into the delivery cycle.
What is Web Application Testing?
็ฝ็ปๅบ็จๆต่ฏ, or website testing, is checking your web application or website for potential bugs before it is made live and is accessible to the general public. Web application testing checks the functionality, usability, security, compatibility, and performance of the web application or website.
During this stage, issues such as web application security, the functioning of the site, its access to handicapped as well as regular users, and its ability to handle traffic are checked.
A website is not one program. It is a stack: HTML, CSS, and JavaScript in the browser, plus APIs and databases on the server. A layer that passes alone can still fail once it talks to its neighbour, so web testing needs complementary techniques.
Types of Web Applications You Need to Test
Before choosing techniques, identify the architecture in front of you. The structure decides where defects concentrate and how you split effort between client and server.
| ๅ่ถ | ๅฎ็่กไธบๆนๅผ | What this means for testing |
|---|---|---|
| ๅ้กตๅบ็จ็จๅบ๏ผSPA๏ผ | Loads once, then updates the view without full page reloads. Gmail works this way. | Most logic ships to the browser: focus on JavaScript state, dynamic rendering, and client-side sessions. |
| Multiple-Page Application (MPA) | Many pages reached through separate route URLs, rendered server-side. Common for e-commerce and news sites. | Navigation paths multiply: test every route, form, and redirect end to end. |
| ๆธ่ฟๅผWebๅบ็จ็จๅบ๏ผPWA๏ผ | Runs like a native app using service workers, a manifest, and an app shell. | Add offline behaviour, stale caches, push notifications, and install prompts. |
Most products mix these patterns. Confirm which one you are dealing with, then work through the eight techniques below.
ๅฆไฝๆต่ฏ Web ๅบ็จ็จๅบๆ็ฝ็ซ
ๅจ่ฝฏไปถๅทฅ็จไธญ๏ผๅฏไปฅๆ นๆฎๆจ็ Web ๆต่ฏ่ฆๆฑๆง่กไปฅไธๆต่ฏ็ฑปๅ/ๆๆฏใ
Each technique can be run manually or by script, and that choice drives cost more than coverage.
| ๆน้ข | ๆๅจๆต่ฏ | ่ชๅจๅๆต่ฏ |
|---|---|---|
| ๆ้ๅ | ๅฏ็จๆงๅ ๆข็ดข ๆฃๆฅ | Regression, cross-browser, load runs |
| Speed on repeat runs | Slow; effort repeats every cycle | Fast; the suite reruns on demand |
| ๆๆฌๆฆๅต | Low upfront, rises every release | Higher upfront, then script maintenance |
1.็ฝ็ซๅ่ฝๆต่ฏ
็ฝ็ซๅ่ฝๆต่ฏ ๆฏไธไธชๅ ๅซๅคไธชๆต่ฏๅๆฐ็่ฟ็จ๏ผไพๅฆ็จๆท็้ขใAPIใๆฐๆฎๅบๆต่ฏใๅฎๅ จๆต่ฏใๅฎขๆท็ซฏๅๆๅกๅจๆต่ฏไปฅๅๅบๆฌ็ฝ็ซๅ่ฝใๅ่ฝๆต่ฏ้ๅธธๆนไพฟ๏ผๅฎๅ ่ฎธ็จๆทๆง่กๆๅจๅ่ชๅจๆต่ฏใๅฎ็จไบๆต่ฏ็ฝ็ซไธๆฏไธชๅ่ฝ็ๅ่ฝใ
Web testing activities include:
ใๆต่ฏใ๏ผTest๏ผ ๆๆ ้พๆฅ ็ฝ้กตไธญ็้พๆฅๆฏๅฆๆญฃๅธธๅทฅไฝ๏ผๅนถ็กฎไฟๆฒกๆๆๅ็้พๆฅใ้่ฆๆฃๆฅ็้พๆฅๅ ๆฌ๏ผ
- ไผ ๅบ้พๆฅ
- ๅ ้จ้พๆฅ
- Anchor ้พๆฅ
- Mail้พๆฅ
ๆต่ฏ่กจๆ ผ ๆญฃๅธธ่ฟ่กใ่ฟๅฐๅ ๆฌ๏ผ
- ่กจๅไธ็่ๆฌๆฃๆฅๅทฅไฝๆญฃๅธธใไพๅฆ๏ผๅฆๆ็จๆทๆชๅกซๅ่กจๅไธญ็ๅฟ ๅกซๅญๆฎต๏ผๅไผๆพ็คบ้่ฏฏๆถๆฏใ
- ๆฃๆฅๆฏๅฆๆญฃๅจๅกซๅ ้ป่ฎคๅผ
- ๆไบคๅ๏ผ่กจๅไธญ็ๆฐๆฎๅฐๆไบคๅฐๅฎๆถๆฐๆฎๅบๆ้พๆฅๅฐๆๆ็็ตๅญ้ฎไปถๅฐๅ
- ่กจๆ ผ็ป่ฟไผๅๆ ผๅผๅ๏ผๆดๆไบ้ ่ฏป
ๆต่ฏ Cookies ๅทฅไฝๆญฃๅธธใCookie ๆฏ็ฝ็ซ็จๆฅ่ฎฐๅฝๆดป่ท็จๆทไผ่ฏ็ๅฐๆไปถ๏ผๅ ๆญคๆจๆ ้ๅจๆฏๆฌก่ฎฟ้ฎ็ฝ็ซๆถ้ฝ็ปๅฝใCookie ๆต่ฏๅฐๅ ๆฌ
- ๅฝๆธ ้ค็ผๅญๆ่พพๅฐ่ฟๆๆถ้ดๆถ๏ผๆต่ฏ cookie๏ผไผ่ฏ๏ผไผ่ขซๅ ้คใ
- ๅ ้ค cookie๏ผไผ่ฏ๏ผๅนถๆต่ฏไธๆฌก่ฎฟ้ฎ่ฏฅ็ฝ็ซๆถๆฏๅฆ่ฆๆฑ่พๅ ฅ็ปๅฝๅญๆฎใ
ๆต่ฏ HTML ๅ CSS ็กฎไฟๆ็ดขๅผๆๅฏไปฅ่ฝปๆพๆๅๆจ็็ฝ็ซใ่ฟๅฐๅ ๆฌ
- ๆฃๆฅ่ฏญๆณ้่ฏฏ
- Readable ่ฒๅฝฉๆนๆก
- ๆ ๅๅ่งๆงใ็กฎไฟ้ตๅฎ W3CใOASISใIETFใISOใECMA ๆ WS-I ็ญๆ ๅใ
ๆต่ฏไธๅกๅทฅไฝๆต็จโ ่ฟๅฐๅ ๆฌ
- ๆต่ฏๆจ็็ซฏๅฐ็ซฏๅทฅไฝๆต/ไธๅกๅบๆฏ๏ผ่ฎฉ็จๆท้่ฟไธ็ณปๅ็ฝ้กตๆฅๅฎๆใ
- ไน่ฆๆต่ฏ่ด้ขๅบๆฏ๏ผ่ฟๆ ทๅฝ็จๆทๆง่กๆๅคๆญฅ้ชคๆถ๏ผWeb ๅบ็จ็จๅบไธญไผๆพ็คบ้ๅฝ็้่ฏฏๆถๆฏๆๅธฎๅฉใ
ๅฏไปฅไฝฟ็จ็ๅทฅๅ ท: QTP , IBM ๅ็็ ๏ผ Selenium
2. ๅฏ็จๆงๆต่ฏ
ๅฏ็จๆงๆต่ฏ ๅทฒ็ปๆไธบไปปไฝๅบไบ Web ็้กน็ฎ็้่ฆ็ปๆ้จๅใๅฎๅฏไปฅ ็ฑๆต่ฏไบบๅ่ฟ่ก ๅๆฌขไฝ ๆไธไธชๅฐๅ็ฆ็นๅฐ็ป ไธ Web ๅบ็จ็จๅบ็็ฎๆ ๅไผ็ธไผผใ
ใๆต่ฏใ๏ผTest๏ผ ็ฝ็ซ ๅฏผ่ช:
- ๆจ็ฝ็ซไธไธๅ้กต้ข็่ๅใๆ้ฎๆ้พๆฅๅบๅจๆๆ็ฝ้กตไธๆธ ๆฐๅฏ่งไธไธ่ด
ใๆต่ฏใ๏ผTest๏ผ ่ฟไธช ๅ ๅฎน:
- ๅ ๅฎนๅบ่ฏฅๆธ ๆฐๆ่ฏป๏ผๆฒกๆๆผๅๆ่ฏญๆณ้่ฏฏใ
- ๅฆๆๅญๅจๅพๅ๏ผๅๅบๅ ๅซโaltโๆๆฌ
ๅฏไปฅไฝฟ็จ็ๅทฅๅ ท: ็ฒ็ฌๆ ่ฎฐ, ๅ ๅฎนๅนฟๅบๅ Clixpy
3. ๆฅๅฃๆต่ฏ
Once features and usability hold up, check that the tiers behind them talk to each other. Three areas to be tested here are โ Application, Web and Database Server
- ๅบ็จ๏ผ ๆต่ฏ่ฏทๆฑๆญฃ็กฎๅ้ๅฐๆฐๆฎๅบ๏ผๅฎขๆท็ซฏ็่พๅบๆญฃ็กฎๆพ็คบใไปปไฝ้่ฏฏ้ฝๅฟ ้กป็ฑๅบ็จ็จๅบๆ่ท๏ผๅนถไธๅช่ฝๆพ็คบ็ป็ฎก็ๅ๏ผ่ไธๆฏๆ็ป็จๆทใ
- Webๆๅกๅจ๏ผๆต่ฏ Web ๆๅกๅจๆญฃๅจๅค็ๆๆๅบ็จ็จๅบ่ฏทๆฑ๏ผๆฒกๆไปปไฝๆๅกๆ็ปใ
- ๆฐๆฎๅบๆๅกๅจ ็กฎไฟๅ้ๅฐๆฐๆฎๅบ็ๆฅ่ฏข็ปๅบ้ขๆ็็ปๆใ
ๆต่ฏ็ณป็ปๅๅบ ๏ผๅฐคๅ ถๆฏ ไธๅฑไน้ด็่ฟๆฅ ๏ผๅบ็จ็จๅบใ็ฝ็ปๅๆฐๆฎๅบ๏ผ ไธ่ฝๆ็ซ ๅนถๅๆ็ป็จๆทๆพ็คบ้ๅฝ็ๆถๆฏใ
ๅฏไปฅไฝฟ็จ็ๅทฅๅ ท: ๆ่ฏบ้ทๅ ๆฏ
4. ๆฐๆฎๅบๆต่ฏ
ๆฐๆฎๅบๆฏ Web ๅบ็จ็จๅบ็ไธไธชๅ ณ้ฎ็ปไปถ๏ผๅฟ ้กปๅฏนๅ ถ่ฟ่กๅฝปๅบๆต่ฏใๆต่ฏๆดปๅจๅ ๆฌ๏ผ
- ๆต่ฏๆง่กๆฅ่ฏขๆถๆฏๅฆๆพ็คบไปปไฝ้่ฏฏ
- ๆถ้ด Integrity ๅจๆฐๆฎๅบไธญๅๅปบใๆดๆฐๆๅ ้คๆฐๆฎๆถ่ฟ่ก็ปดๆคใ
- ๆฃๆฅๆฅ่ฏข็ๅๅบๆถ้ด๏ผๅนถๆ นๆฎ้่ฆ่ฟ่กๅพฎ่ฐใ
- ไปๆฐๆฎๅบๆฃ็ดขๅฐ็ๆต่ฏๆฐๆฎๅ็กฎๆพ็คบๅจๆจ็ Web ๅบ็จ็จๅบไธญ
ๅฏไปฅไฝฟ็จ็ๅทฅๅ ท: QTP, Selenium
5. ๅ ผๅฎนๆงๆต่ฏ
Compatibility testing ensures your web application displays and behaves correctly across different devices. This includes:
ๆต่งๅจๅ ผๅฎนๆงๆต่ฏ๏ผๅไธไธช็ฝ็ซๅจไธๅๆต่งๅจไธ็ๆพ็คบๆๆไผๆๆไธๅใๆจ้่ฆๆต่ฏๆจ็ Web ๅบ็จ็จๅบๆฏๅฆๅจๅไธชๆต่งๅจไธๆญฃ็กฎๆพ็คบ๏ผ Java่ๆฌใAJAX ๅ่บซไปฝ้ช่ฏ่ฟ่กๆญฃๅธธใๆจ่ฟๅฏไปฅๆฃๆฅ ็ต่ฏ ๆต่งๅจๅ ผๅฎนๆงใ
ๆ้ฎใๆๆฌๅญๆฎต็ญ Web ๅ ็ด ็ๆธฒๆไผ้็ ่ฟ่ก็ณป็ป. ็กฎไฟๆจ็็ฝ็ซ่ฝๅคๅพๅฅฝๅฐ้ๅบๅ็ง็ปๅ Opera็ณป็ป๏ผๅฆ WindowsใLinuxใMac ๅๆต่งๅจ๏ผไพๅฆ FirefoxใInternet ExplorerใSafari ็ญใ
ๅฏไปฅไฝฟ็จ็ๅทฅๅ ท: Dynatrace
6. ๆง่ฝๆต่ฏ
This will ensure your site works under all loads. Testing activities will include but not limited to โ
- ไธๅ่ฟๆฅ้ๅบฆไธ็็ฝ็ซๅบ็จ็จๅบๅๅบๆถ้ด
- ่ด่ฝฝๆต่ฏไฝ ็ Web ๅบ็จ็จๅบไปฅ็กฎๅฎๅ ถๅจๆญฃๅธธๅๅณฐๅผ่ด่ฝฝไธ็่กไธบ
- ๅฏนๆจ็็ฝ็ซ่ฟ่กๅๅๆต่ฏ๏ผไปฅ็กฎๅฎๅจ้ซๅณฐๆถๆฎต่ถ ๅบๆญฃๅธธ่ด่ฝฝๆถ็ๆญ็นใ
- ๆต่ฏๅฆๆ็ฑไบๅณฐๅผ่ด่ฝฝ่ๅ็ๅดฉๆบ๏ผ็ซ็นๅฆไฝไปๆญค็ฑปไบไปถไธญๆขๅค
- ็กฎไฟๅฏ็จ gzip ๅ็ผฉใๆต่งๅจๅๆๅกๅจ็ซฏ็ผๅญ็ญไผๅๆๆฏ๏ผไปฅๅๅฐๅ ่ฝฝๆถ้ด
ๅฏไปฅไฝฟ็จ็ๅทฅๅ ท: Loadrunner, JMeter
7. ๅฎๅ จๆต่ฏ
ๅฎๅ จๆต่ฏ ๅฏนไบๅญๅจไฟก็จๅก็ญๆๆๅฎขๆทไฟกๆฏ็็ตๅญๅๅก็ฝ็ซๆฅ่ฏด๏ผๆต่ฏ่ณๅ ณ้่ฆใๆต่ฏๆดปๅจๅ ๆฌ๏ผ
- ๆต่ฏไธๅบๅ ่ฎธๆช็ปๆๆ่ฎฟ้ฎๅฎๅ จ้กต้ข
- ๅฆๆๆฒกๆ้ๅฝ็่ฎฟ้ฎๆ้๏ผๅไธๅบไธ่ฝฝๅ้ๆไปถ
- ็จๆท้ฟๆถ้ดไธๆดปๅจๅๆฃๆฅไผ่ฏไผ่ชๅจ็ปๆญข
- ไฝฟ็จ SSL ่ฏไนฆๆถ๏ผ็ฝ็ซๅบ้ๅฎๅๅฐๅ ๅฏ็ SSL ้กต้ขใ
Intruder
Intruder ๆฏไธๆฌพๅ่ฝๅผบๅคง็ๆผๆดๆซๆๅจ๏ผๅฏๅธฎๅฉๆจๅ็ฐๆฝไผๅจ Web ๅบ็จ็จๅบๅๅบๅฑๅบ็ก่ฎพๆฝไธญ็ไผๅคๆผๆดใๆไพไธ็้ขๅ ็ๅฎๅ จๆฃๆฅใๆ็ปญ็ๆงๅๆไบไฝฟ็จ็ๅนณๅฐ๏ผ Intruder ไฟๆคๅ็ง่งๆจก็ไผไธๅ ๅ้ปๅฎขๆปๅปใ
ไบงๅ็นๆง
- ไธๆต็ๅจ่่ฆ็่ๅด๏ผ่ถ ่ฟ 10,000 ๆฌกๅฎๅ จๆฃๆฅ
- ๆฃๆฅ้ ็ฝฎ็ผบ้ทใ็ผบๅคฑ่กฅไธใๅบ็จ็จๅบ็ผบ้ท๏ผๅฆ SQL ๆณจๅ ฅๅ่ทจ็ซ็น่ๆฌ๏ผ็ญ
- ่ชๅจๅๆๅนถ็กฎๅฎๆซๆ็ปๆ็ไผๅ ๆฌกๅบ
- ็้ข็ด่ง๏ผ่ฎพ็ฝฎๅฟซ้๏ผๅฏ่ฟ่ก้ฆๆฌกๆซๆ
- ไธปๅจๅฎๅ จ็ๆงๆๆฐๆผๆด
- AWS, Azureๅ Google Cloud ่ฟๆฅๅจ
- API ไธๆจ็ CI/CD ็ฎก้้ๆ
8. ไบบ็พคๆต่ฏ
You will select a large number of people (crowd) to execute tests which otherwise would have been executed by a small in-house group. Crowdsourced testing is an interesting and upcoming concept and helps unravel many an unnoticed defect.
ๅฏไปฅไฝฟ็จ็ๅทฅๅ ท: ไผๅ ๆต่ฏๅนณๅฐ
Web Application Testing Process: Step-by-Step
The eight techniques tell you what to check. The process below tells you when to run them.
- Gather and clarify requirements. List what the application must do and how it should behave. Ambiguous requirements produce untestable expectations, so resolve them first. This step anchors web testing in the wider ่ฝฏไปถๆต่ฏ็ๅฝๅจๆ.
- Write the test plan. Decide which techniques apply, who runs them, which tools are needed, and on what timeline. The plan is your roadmap and your estimate.
- Develop test cases. Turn each requirement into concrete steps with expected results, covering both the happy path and the negative scenarios users trigger by accident.
- Set up the test environment. Mirror production as closely as budget allows: the same browser and operating system pairs, comparable data volumes, realistic network speeds.
- Execute the tests. Run the cases, record actual against expected results, and capture screenshots, console output, and server logs while the failure is still reproducible.
- ๆฅๅๅ track็ผบ้ทใ Log each one with steps to reproduce and a priority, then retest after the fix and confirm nothing nearby broke.
- Close the cycle. Produce a test summary covering what was tested, what was found, what remains open, and what to improve, then sign off for release.
โ ๏ธ Plan the schedule, not just the tests: Web testing is arduous, and deadline pressure is the obstacle you hit first, followed by repeated code changes that invalidate finished work. Define every task in step 2 and build a work chart from it.
