Web Testing: Complete guide on testing web applications

In my previous post I have outlined points to be considered while testing web applications. Here we will see some more details on web application testing with web testing test cases. Let me tell you one thing that I always like to share practical knowledge, which can be useful to users in their career life. This is a quite long article so sit back and get relaxed to get most out of it.

Let’s have first web testing checklist.
1) Functionality Testing
2) Usability testing
3) Interface testing
4) Compatibility testing
5) Performance testing
6) Security testing

1) Functionality Testing:

Test for - all the links in web pages, database connection, forms used in the web pages for submitting or getting information from user, Cookie testing.

Check all the links:

  • Test the outgoing links from all the pages from specific domain under test.
  • Test all internal links.
  • Test links jumping on the same pages.
  • Test links used to send the email to admin or other users from web pages.
  • Test to check if there are any orphan pages.
  • Lastly in link checking, check for broken links in all above-mentioned links.

Test forms in all pages:
Forms are the integral part of any web site. Forms are used to get information from users and to keep interaction with them. So what should be checked on these forms?

  • First check all the validations on each field.
  • Check for the default values of fields.
  • Wrong inputs to the fields in the forms.
  • Options to create forms if any, form delete, view or modify the forms.

Let’s take example of the search engine project currently I am working on, In this project we have advertiser and affiliate signup steps. Each sign up step is different but dependent on other steps. So sign up flow should get executed correctly. There are different field validations like email Ids, User financial info validations. All these validations should get checked in manual or automated web testing.

Cookies testing:
Cookies are small files stored on user machine. These are basically used to maintain the session mainly login sessions. Test the application by enabling or disabling the cookies in your browser options. Test if the cookies are encrypted before writing to user machine. If you are testing the session cookies (i.e. cookies expire after the sessions ends) check for login sessions and user stats after session end. Check effect on application security by deleting the cookies. (I will soon write separate article on cookie testing)

Validate your HTML/CSS:
If you are optimizing your site for Search engines then HTML/CSS validation is very important. Mainly validate the site for HTML syntax errors. Check if site is crawlable to different search engines.

Database testing:
Data consistency is very important in web application. Check for data integrity and errors while you edit, delete, modify the forms or do any DB related functionality.
Check if all the database queries are executing correctly, data is retrieved correctly and also updated correctly. More on database testing could be load on DB, we will address this in web load or performance testing below.

2) Usability Testing:

Test for navigation:
Navigation means how the user surfs the web pages, different controls like buttons, boxes or how user using the links on the pages to surf different pages.
Usability testing includes:
Web site should be easy to use. Instructions should be provided clearly. Check if the provided instructions are correct means whether they satisfy purpose.
Main menu should be provided on each page. It should be consistent.

Content checking:
Content should be logical and easy to understand. Check for spelling errors. Use of dark colors annoys users and should not be used in site theme. You can follow some standards that are used for web page and content building. These are common accepted standards like as I mentioned above about annoying colors, fonts, frames etc.
Content should be meaningful. All the anchor text links should be working properly. Images should be placed properly with proper sizes.
These are some basic standards that should be followed in web development. Your task is to validate all for UI testing

Other user information for user help:
Like search option, sitemap, help files etc. Sitemap should be present with all the links in web sites with proper tree view of navigation. Check for all links on the sitemap.
“Search in the site” option will help users to find content pages they are looking for easily and quickly. These are all optional items and if present should be validated.

3) Interface Testing:
The main interfaces are:
Web server and application server interface
Application server and Database server interface.

Check if all the interactions between these servers are executed properly. Errors are handled properly. If database or web server returns any error message for any query by application server then application server should catch and display these error messages appropriately to users. Check what happens if user interrupts any transaction in-between? Check what happens if connection to web server is reset in between?

4) Compatibility Testing:
Compatibility of your web site is very important testing aspect. See which compatibility test to be executed:

  • Browser compatibility
  • Operating system compatibility
  • Mobile browsing
  • Printing options

Browser compatibility:
In my web-testing career I have experienced this as most influencing part on web site testing.
Some applications are very dependent on browsers. Different browsers have different configurations and settings that your web page should be compatible with. Your web site coding should be cross browser platform compatible. If you are using java scripts or AJAX calls for UI functionality, performing security checks or validations then give more stress on browser compatibility testing of your web application.
Test web application on different browsers like Internet explorer, Firefox, Netscape navigator, AOL, Safari, Opera browsers with different versions.

OS compatibility:
Some functionality in your web application is may not be compatible with all operating systems. All new technologies used in web development like graphics designs, interface calls like different API’s may not be available in all Operating Systems.
Test your web application on different operating systems like Windows, Unix, MAC, Linux, Solaris with different OS flavors.

Mobile browsing:
This is new technology age. So in future Mobile browsing will rock. Test your web pages on mobile browsers. Compatibility issues may be there on mobile.

Printing options:
If you are giving page-printing options then make sure fonts, page alignment, page graphics getting printed properly. Pages should be fit to paper size or as per the size mentioned in printing option.

5) Performance testing:
Web application should sustain to heavy load. Web performance testing should include:
Web Load Testing
Web Stress Testing

Test application performance on different internet connection speed.
In web load testing test if many users are accessing or requesting the same page. Can system sustain in peak load times? Site should handle many simultaneous user requests, large input data from users, Simultaneous connection to DB, heavy load on specific pages etc.

Stress testing: Generally stress means stretching the system beyond its specification limits. Web stress testing is performed to break the site by giving stress and checked how system reacts to stress and how system recovers from crashes.
Stress is generally given on input fields, login and sign up areas.

In web performance testing web site functionality on different operating systems, different hardware platforms is checked for software, hardware memory leakage errors,

6) Security Testing:

Following are some test cases for web security testing:

  • Test by pasting internal url directly into browser address bar without login. Internal pages should not open.
  • If you are logged in using username and password and browsing internal pages then try changing url options directly. I.e. If you are checking some publisher site statistics with publisher site ID= 123. Try directly changing the url site ID parameter to different site ID which is not related to logged in user. Access should denied for this user to view others stats.
  • Try some invalid inputs in input fields like login username, password, input text boxes. Check the system reaction on all invalid inputs.
  • Web directories or files should not be accessible directly unless given download option.
  • Test the CAPTCHA for automates scripts logins.
  • Test if SSL is used for security measures. If used proper message should get displayed when user switch from non-secure http:// pages to secure https:// pages and vice versa.
  • All transactions, error messages, security breach attempts should get logged in log files somewhere on web server.

I think I have addressed all major web testing methods. I have worked for around 2 years out of my testing career on web testing. There are some experts who have spent their whole career life on web testing. If I missed out addressing some important web testing aspect then let me know in comments below. I will keep on updating the article for latest testing information.

If you like this article you would also like to subscribe to our software testing email newsletter for software testing latest updates.




Related Posts:

  • Difference between Desktop, Client server and Web testing
  • What if there isn’t enough time for thorough testing
  • REMEMBER SOFTWARE TESTING 10 RULES
  • Interesting posts on Software Testing Help
  • Smoke testing and sanity testing - Quick and simple differences
  • 107 comments ↓

    #1 swapna on 08.16.07 at 2:18 pm

    Very useful guide on web application testing….
    Thank u sooo much

    #2 testerqa on 08.16.07 at 4:22 pm

    Very useful tutorial

    #3 Sameer Mandve on 08.17.07 at 2:42 am

    Really nice one………..

    #4 jignesh on 08.18.07 at 5:22 am

    hi, Which one tool is best for testing and easy to use. give introduction about this tool and perfect Details.
    Thanks

    #5 Vijay on 08.20.07 at 5:44 am

    Thanks Swapna, TesterQA and Sameer for your kind words.

    @ Jignesh Automation tool selection is purely based on the project which you are going to test. I suggest what all factors should be considered while choosing automation tool for your project in this article :
    http://www.softwaretestinghelp.....anization/

    Still I will try to cover in my posts about the main automation tools like WinRunner and QTP.

    #6 We application testing - SURESHKUMAR.NET FORUMS on 08.20.07 at 8:16 am

    […] testing Very good summary of web testing. See the details of every point of web testing here.. Complete guide on Web testing __________________ Ask me your Software Testing Queries! […]

    #7 ASHA on 08.20.07 at 10:16 am

    HI,

    Very useful information. Thank you.

    #8 jhenz on 08.22.07 at 2:04 am

    wow! what an informative site… i am really thankful for this. as i’ve said before, i have learned a great deal on these infos. again, a lot of thanks! i’ve done all 5 checklist except for the security… now that u hav the details on how i’l do the checking, i wil defntly try it. thank you again… :D

    #9 jhenz on 08.22.07 at 6:38 am

    hello vijay,

    i would like to ask when are you going to post the article about cookies?… i am going to do a test on cookies soon and before i do this, i would like to read first your article. but f incase my testing would me much sooner, i just would like to ask how would you do this… “Test the application by enabling or disabling the cookies in your browser options.”

    thank you very much! :)

    #10 Vijay on 08.22.07 at 7:04 am

    @Asha Thank for your kind words..

    @ Jhenz yeah I will try ASAP to write Cookie testing article..
    About your query - To change cookie settings in Internet Explorer: Open IE-Go to Tools-Internet Options- Click on Privacy tab- then ‘Advanced’ button. Here you can enable or disable the cookies.
    For Firefox Go to Tools-Options-Privacy

    #11 jhenz on 08.22.07 at 7:39 am

    thank you again. :D

    #12 udhayakumar on 08.22.07 at 9:02 am

    Total summary of testing very good.

    #13 Naga Vishala on 08.27.07 at 11:18 am

    Hi, this is naga vishala

    I would like to know that can we write test cases for non-functionality testing?(like User Acceptence Testing)
    And one more What is Monkey Testing ? shall we use this testing in real time?

    #14 Vijay on 09.03.07 at 8:49 am

    @ Naga vishala - Yes we should write test cases for usability testing also. Monkey testing is random , destructive type testing performed by some automation tools and without driven by any real user. Monkey testing can generally find the crashes in application.

    #15 yemi on 09.05.07 at 9:47 am

    I have just finished a course intesting using test director. I don,t have job exp, how can i go about geting a job or geting jo exp

    #16 Kishore on 09.07.07 at 10:59 am

    Hi,
    Excellent stuff.
    I would like to ask one question regarding performance testing. Can we perform performance testing manually. as you mention about web stress testing where we stress input file, sign up screen etc. So, how we gona perform that as we all know sign up page has already has validation. Please elaborate this concept a bit.

    Thanks & Regards
    Kishore

    #17 Ramdev Sharma on 09.11.07 at 8:02 am

    hi,
    Really excellent site.This site gives the information according to the real time.it’s very usefull.
    Can you please write on How To analyze the results of Load Testing? ,What are the points to be consider for load testing?
    Please write indepth regarding “Load Testing”.
    Keep up the good work…..
    Thanks in Advance…

    #18 Trupti Gandhi on 09.17.07 at 6:32 am

    hi
    very informative information thank you very much

    i want to know more on Regression testing & performation testing

    on Theoritical point of view i got but i want to know how can i test these 2 things practiclly

    #19 lavanya on 09.17.07 at 6:39 am

    what is orphan link,broken link , internal link, externallink .
    give with examples

    #20 lavanya on 09.17.07 at 6:42 am

    what are different levels of people involved in a company for software testing. what are their position names starting from the tester.

    #21 Naveen Pathak on 09.17.07 at 7:37 am

    Very Nice,
    can you add SQL injection and Session hijacking in security testing.

    #22 lavanya on 09.18.07 at 5:11 am

    your articals are really great . i would like to ask what is quiet phase in sdlc.

    #23 shweta on 09.21.07 at 5:19 am

    Hi,
    Ur information is indeed very helpful.Can u please tell me ,hw can we perform cookie,html &css testing.

    #24 shweta on 09.21.07 at 6:12 am

    what r the best automated tools for web testing????

    #25 pradeep mathew on 09.22.07 at 2:40 pm

    how we can test what is the maximum users that can access a particular web site at a time???

    #26 Good job on 09.28.07 at 12:22 pm

    good job,if interaction is done or chat is provide we can learn nice informations on testing .

    Because i believe testing is innovative,every person will have his own creations what ever we see or learn ,while in implementation we loose the ethics on that particular concept ,so the person intrested can chat and solve the doubts regarding testing

    #27 Vijay on 10.03.07 at 9:34 am

    @ -Kishore
    The only way is to do performance testing on pages having Captcha is to disable the Captcha while recording the script using automation tool. Disabling Captcha will not effect on your performance standards as your final goal is to stress the system for its resources.

    @ Ramdev Sharma
    Yes to explain about Load testing I need to write a article on it as this topic itself is a big one.

    @ Trupti Gandhi
    For regression testing using automation tool is the best and efficient method. However you need some test cases written on the module you are going to test for regression. You can use old test cases to record the scripts on.
    For performance testing tools mentioned here http://www.opensourcetesting.org/performance.php
    First decide your performance criteria and then apply the test cases accordingly

    @ lavanya
    On every page there are some links pointing to some pages. So we can differentiate all these links.
    The links pointing to same domain are said to internal links. e.g The link http://www.softwaretestinghelp.com/jobs/ is pointing to same domain softwaretestinghelp.com so it’s a internal link.
    Links pointing to other domain are external links. E.g See the above link pointing to opensourcetesting.org domain.
    Broken links: If clicking on any link displays 404 page not found error then that link is said to be broken or unreachable link.
    Orphan link: If no internal link is pointing to any particular web page on your domain then that web page link is said to be orphan link i.e not having any ancestor and no way to reach that link from your domain !

    @shweta
    for Cookie testing you can refer the article
    http://www.softwaretestinghelp.....est-cases/

    @ pradeep mathew
    You can use load or stress testing automation tools to simulate n number of virtual users accessing particular web page or site simultaneously.

    #28 vamsi on 10.03.07 at 10:38 am

    hai can any one suggest free online testing books for download?

    #29 Balister Panwar on 10.08.07 at 1:38 pm

    hai. what is main point for security testing for web application

    #30 Raji on 10.09.07 at 11:15 am

    Hi Vijay,
    Firstly, this site is very helpful for beginners.
    All your posts are very easy to understand and have in depth information.
    I would be thankful if you could suggest some simple websites / software etc that beginners could test at home to understand all the concepts better.
    Thanks,
    Raji

    #31 Kaustubh on 10.17.07 at 11:12 am

    Hi Vijay,

    This site is very helpful.. Can you please explain what is “Validate your HTML/CSS”.

    And what are the questions asked on web based testing.

    Thanks

    Kaustubh

    #32 Giridhara Reddy on 10.23.07 at 4:30 am

    This is very useful information. This page is going to be part of my favorites.

    Thank you
    Giridhara Reddy.S

    #33 sri on 10.23.07 at 12:32 pm

    This website is the best website i ever been visited.
    lots of useful information for every one.

    Thanks,
    Sri.

    #34 udhayakumar on 10.30.07 at 7:04 am

    Hi
    This is very use ful information.

    thanks
    udhaya

    #35 Robinson on 10.31.07 at 6:54 am

    Really this site is awesome.. Very useful information.. I love this site.. Thanks a lot..

    #36 Priya on 11.05.07 at 11:26 pm

    Hi Vijay,

    Really this is a excellent site for all of us. The information are really very practical. I am very much thankful for this.
    Could you please help me to prepare a testing strategy for Microsoft Office SharePoint Server 2007 (MOSS 2007). I mean how do I approach for this and what should be my strategy??

    Thanks in advance.

    Priya

    #37 ARPITHA on 11.16.07 at 6:13 am

    I LIKETHIS WEB SITE VERY MUCH BUT IWANT TO KNOE HOW TO TEST MICROSOFT WORD IN SOFTWARE TESTING
    PLEASE GUIDE ME AND SHOW ME THE TEST CASES.

    #38 ARPITHA on 11.16.07 at 6:14 am

    GOOD WEBSITE

    #39 Ajay on 11.18.07 at 11:09 am

    Can anyone tell me about the automation tools for load testing and stress testing.

    #40 Manju.P on 11.19.07 at 6:13 am

    Please note that there is a spelling mistake for the word user status in the last line

    Cookies testing:
    if the cookies are encrypted before writing to user machine. If you are testing the session cookies (i.e. cookies expire after the sessions ends) check for login sessions and user stats after session end.

    #41 Tulsi Akula on 11.19.07 at 7:19 am

    Cookies testing:
    if the cookies are encrypted before writing to user machine. If you are testing the session cookies (i.e. cookies expire after the sessions ends) check for login sessions and user status after session end.

    #42 Manju.P on 11.20.07 at 4:55 am

    Please check and correct the spelling mistake for the word others status in the last line of the second case in security testing

    6) Security Testing:

    Following are some test cases for web security testing:

    Try directly changing the url site ID parameter to different site ID which is not related to logged in user. Access should denied for this user to view others stats.

    #43 Vijay on 11.20.07 at 5:40 am

    @ Manju,
    It’s not a spelling mistake. I have used word ’stats’ as an abbreviation for word ’statistics’ which here means data reports for user account and this word ’stats’ is commonly used in online advertising business.

    #44 Good 1 on 11.20.07 at 6:57 am

    Good Site

    #45 Manju.P on 11.21.07 at 3:49 am

    Vijay,
    Thanks for the information

    #46 shiva on 11.21.07 at 9:20 am

    thanks

    #47 Ajay on 11.21.07 at 5:16 pm

    How to perform database testing.

    #48 daredevil on 11.22.07 at 3:52 am

    hey vijay,
    I find this website very helpful ….thnx alot . I was waiting for a answer on validation of HtML/CSS which was posted by Kaustubh as even i wanted to know more abt the HtMl/css and wat role it has in search engines.

    thnx

    #49 daredevil on 11.22.07 at 4:14 pm

    hey vijay,
    i would also like to know how test a search field with the first name and last name …..and wat are the possible scenarios can we try???

    #50 Tanvi on 11.26.07 at 12:30 pm

    vijay, wat do u mean by “Check if site is crawlable to different search engines.”

    #51 tulasi on 11.28.07 at 9:47 am

    hi this tulasiram
    i am new to this testing,
    i have a dought in web testing.
    Right now u r useing yahoo application, not only you
    so many users are useing this application . How can
    you test this application.

    #52 Debasis on 12.03.07 at 7:07 am

    I have a similar article called Website Testing Cheat-Sheet! Hope you would find it interesting!

    Happy Testing…

    #53 venkat on 12.04.07 at 5:36 am

    hi thanks for the team, can develop more using this

    #54 Pradeep on 12.04.07 at 8:47 am

    HI ,

    This is very much useful and Thanks for this article

    #55 Varsha on 12.11.07 at 7:18 am

    Hi Vijay!

    Excellent website. Thanks a lot.

    Could you pls elaborate more on Stress Testing & how to perform it manually?

    Also can anyone tell me about some good open-source tools for functional testing?

    #56 Malatesh on 12.24.07 at 11:48 am

    hi
    i felt this site is very useful and is there any free tool available on net to do the performance and stress testing…which should be easy to understand

    #57 Firon Fitz on 01.03.08 at 4:38 pm

    This information is very useful fot me nut can you tell more about cookie, html and css testing?

    #58 shankar on 01.05.08 at 4:19 pm

    please give me some sample testcases for web application testing.

    #59 mugi on 01.07.08 at 5:38 am

    It’s very easy to learn the testing concepts in the clear way.Each and every concept is undestands very easily and clearly.If you’r providing Sample testcase,bug report and tseting deliverables useful for us!!!!!!

    Tahnk you!!!!

    #60 Somendra Singh on 01.08.08 at 11:45 am

    It is a good article that really help me to understand the Website Testing.

    Thank You!!!!

    #61 JAYANT on 01.08.08 at 12:44 pm

    THANKS FOR INFORMATION

    #62 renji on 01.18.08 at 5:38 am

    great stuff…i want to know more abt how to test web based application using QTP

    #63 guest on 01.25.08 at 5:23 am

    hi
    i am working as tester with 2+ of exp in manual testing only.
    up to uploading the resume and shortlisting the resume,every thing is working correctly.but after that i am not getting any proper reply.
    i don’t know is mistake from my side i mean from my resume and skills or problem from company side
    please give me the reply
    thanku in advance

    #64 Madhavi on 01.30.08 at 12:05 pm

    Very useful information. Thanks so much!

    #65 karthik on 02.05.08 at 5:07 pm

    very useful tips to learn web testing

    #66 Mitu on 02.11.08 at 7:15 am

    Hi,

    This article is really great. Keep on publishing these kind.
    thanks

    #67 SOUJANYA on 02.12.08 at 10:16 am

    Not clear about mobile browsing

    #68 shamita on 02.14.08 at 5:45 am

    Hi,

    I wanted to know that how should I start the web testing at work. Like there are so many versions of IE , should I test for all the versions in compatabillity testing. I am very confused, I have no experience and I got a job in web testing …Please help me.

    Shamita

    #69 mohammad on 02.14.08 at 8:02 am

    Thanks for sending its help us

    #70 Sachin on 02.20.08 at 6:23 pm

    Good job done.

    But the main thing is that when u would like to test all these?

    Means which is your schedule, importance for doing all these test?

    #71 DILeeP on 02.21.08 at 10:44 pm

    This is really nice material I’ve seen so far.
    Thats really great job done by softwaretestinghelp.
    Really appretiable…n commendable…
    Thanks a lot.

    #72 Prasanna on 02.22.08 at 5:05 am

    Hi, this is prasanna
    All u r experiences talks on u r article.. easy to understand.. … every web testers should read this…..

    #73 prasanna on 02.26.08 at 6:40 am

    How to test that whether cookies are encrpted before writing to the user machine???? Please let me know the answer

    #74 Sashi on 03.03.08 at 4:58 am

    Your site rocks. It is by far the best site related to Software Testing. My sincere appreciations and good wishes for your entire team.

    #75 selvam on 03.05.08 at 1:15 pm

    I am going to start my carrier in testing and doing a course in chennai.
    where can i get sample applications(projects) for practising manual testing.

    Please can anyone send me info about it,i will be grateful……..

    Thanks in advance

    selvam.ba@rediffmail.com

    #76 selvam on 03.05.08 at 1:17 pm

    Sashi you have given the perfect opinion…

    same

    #77 Sridhar on 03.07.08 at 4:36 pm

    Hey, I am doing my M.C.A final year and i have chosen webserver performance testing as my curriculum project, but i am unable to understand what to do and where to start from. PlZ help me by telling me what to do. Thank you. and also plz tell me the name of the sites that has uml diagrams for web server testing. Thank you once again

    #78 sanjeev rai on 03.11.08 at 6:25 am

    Iam 37,an under graduate, and want to become a software taster.What are my chances of getting a job in the Gulf countries or New Zealand as a software tester?

    #79 sanjeev rai on 03.11.08 at 6:27 am

    Waiting for a reply.Thank you.

    #80 Sally4000 on 03.11.08 at 11:47 am

    Hello ,
    Thanks for the useful article.
    I would like to ask you if you can help me with Automated testing of applications for Microsoft Office SharePoint Server2007.
    I’m new to sharepoint and I don’t have any idea what I have to do!

    If I can have your help for the strat?
    Looking forward to receiving your email

    Many Thanks

    #81 raghavendra tc on 03.12.08 at 11:58 am

    superb explonation on web testing., thank u very much..
    and also i need to ask one more que–>

    plz explain on unit & ,whitebox &,regression testing

    currently am working on black box & UAT testing.,
    and also explain me about QTP automation

    plzzzzzzzzzzzzz

    regards
    raghu

    #82 Tejas on 03.12.08 at 1:22 pm

    What about concurrency testing how to write effective test cases for the same ?

    #83 Amita on 03.20.08 at 6:59 am

    A very nice ,informative and usefule website

    #84 manjula on 03.24.08 at 11:50 am

    Hi this is very much useful for web testing i have learnt so much from this article. please update if any things are there on web testing.

    #85 manjula(manu) on 03.24.08 at 11:52 am

    Please any one can tell me the difference between the difference between build and version?

    #86 meenu on 03.24.08 at 9:17 pm

    please give detail demo on tools.

    good info

    #87 nisha on 03.27.08 at 11:01 am

    new and handy information provided…

    #88 shaikh on 03.27.08 at 11:03 am

    hey , u had done a great job..
    its really helpful… thanks

    #89 shaikh on 03.27.08 at 11:04 am

    is thr any way to test performance manually..

    #90 Hasini on 04.02.08 at 9:39 am

    I am working as a tester in elearning division. i need to know about software testing , prepartion of test cases and test plan.

    Please provide me all the relevant details about test case preparations.

    #91 Navin Singh on 04.06.08 at 6:39 pm

    Hi,
    This is very usefull website for me. I learnt a lot of techniques. May be this is not much usefull site for some people but for me it’s very usefull and meanning full site. I’m very thankfull to owner of this site for providing me a really good learning platform.
    Thanks for all

    #92 Sashi Mohan on 04.08.08 at 12:05 pm

    Hi,
    good effort!
    Please add cross site scripting, sql injection etc information. that will be more helpful for newbies.

    #93 Sachin on 04.09.08 at 6:49 am

    A wonderfull and very informative site for web testing.Thanks a lot

    #94 Raghavendra NK on 04.11.08 at 9:23 am

    Good information about web application testing.

    We can always go the next level detail of how to perform different kinds of testing mentioned above…

    But a good article to begin with…

    #95 Bebs on 04.18.08 at 4:05 am

    Essential online tips for website testers…. thank you for this useful information.

    #96 chssekharrao on 04.19.08 at 1:44 pm

    plz tell me web testing in qtp

    #97 bhavya on 04.22.08 at 6:26 am

    Hi
    This site is really good.I didnt understand following description about security testing.Pls reply me

    Web directories or files should not be accessible directly unless given download option.
    Test the CAPTCHA for automates scripts logins.
    Test if SSL is used for security measures. If used proper message should get displayed when user switch from non-secure http:// pages to secure https:// pages and vice versa.
    All transactions, error messages, security breach attempts should get logged in log files somewhere on web server

    #98 atiw on 04.24.08 at 8:41 pm

    @ bhavya, i am not a tester yet but i would try to answer you. for example in a bank’s website, there should be a link to download a loan application pdf file and any user should not be able to access this or any other file by directly typing the address in the browser.
    If it is accesible, it is non-secure and vulnerable.

    CAPTCHA are challenging questions generated by machines to be responded by humans and not by machines, to make sure that the attempt to access is by a human and not by a bot. If CAPTCHA is enabled in a web login, it has to be tested.

    SSL is a cryptographic protocol for securing HTTP communication over the internet. When user switches from HTTP to HTTPS or vice-versa, a message window is pops up to inform about this switching and do you want to continue.

    Log files should be maintained to recording and future analysis of all web activities, so that corrective and preventive measures could be taken.

    @ For Vijaya and all testers, please correct my knowledge, where wrong.

    #99 atiw on 04.24.08 at 8:49 pm

    @ manjula (manu), i am not a tester yet but i would try to answer you.

    Builds are program codes which developers deliver from time to time to the testers, while version is the complete application delivered to the end users.

    Adding to this, there are also multiple releases with slight improvements in a version.

    @ For Vijaya and all testers, please correct my knowledge, where wrong.

    #100 AJAY on 04.30.08 at 10:48 am

    can any one tell me about database testing in a clear way.

    #101 Vishal Chhaperia on 05.02.08 at 4:56 am

    Hi All,

    If any of u is working on Unit test then Pls help me out , act. i need to develop a test case on unit testing, I have the SRS as only thing with so Pls tell me how to procced.

    Hopeing for early reply!

    Thanks

    Vishal
    call: 09830704327
    mail: bishalchaperia@gmail.com

    #102 VIJAYD on 05.02.08 at 9:59 am

    Hi All,

    Hope this helps…

    Q: What is the difference between client-server testing and web based testing and what are things that we need to test?

    Ans: Projects are broadly divided into two types of:
    2 tier applications
    3 tier applications

    CLIENT / SERVER TESTING
    [a] This type of testing usually done for 2 tier applications (usually developed for LAN)
    Here we will be having front-end and backend.

    The application launched on front-end will be having forms and reports which will be monitoring and manipulating data

    Eg : applications developed in VB, VC++, Core Java, C, C++, D2K, PowerBuilder etc.,
    The backend for these applications would be MS Access, SQL Server, oracle, sybase, mysql, quadbase

    The tests performed on these type of applications would be
    - user interface testing
    - manual support testing
    - Functionality testing
    - compatability testing & configuration testing
    - intersystems testing

    WEB TESTING
    [b] This is done for 3 tier applications (developed for Internet / intranet / xtranet)

    Here we will be having Browser, web server and DB server.

    The applications accessible in browser would be developed in HTML, DHTML, XML, JavaScript etc.,
    (we can monitor thru these applications)

    Applications for the web server would be developed in Adv Java, ASP, JSP, VBScript, JavaScript, Perl, Cold Fusion, PHP etc.,
    (all the manipulations are done on the web server with the help of these programs developed)

    The DBserver would be having oracle, sql server, sybase, mysql etc.,
    (all data is stored in the database available on the DB server)

    The tests performed on these type of applications would be
    - user interface testing
    - Functionality testing
    - security testing
    - browser compatability testing
    - load / stress testing
    - interoperability testing/intersystems testing
    - storage and data volume testing

    A web-application is a three tier application.
    This has a browser (monitors data) [monitoring is done using html, dhtml, xml, javascript]-> webserver (manipulates data) [ manipulations are done using programming languages or scripts like adv java, asp, jsp, vbscript, javascript, perl, coldfusion, php] -> database server (stores data) [data storage and retrieval is done using databases like oracle, sql server, sybase, mysql] .

    The types of tests which can be applied on this type of applications are:
    1. User interface testing for validation & user friendliness
    2. Functionality testing to validate behaviors, i/p, error handling, o/p, manipulations, services levels, order of functionality, links, content of web page & backend coverage’s
    3. Security testing
    4. Browser compatability
    5. Load / stress testing
    6. Interoperability testing
    7. Storage & data volume testing

    a client-server application is a two tier application.
    This has forms & reporting at front-end (monitoring & manipulations are done) [ using vb, vc++, core java, c, c++, d2k, power builder etc.,] -> database server at the backend [data storage & retrieval) [ using ms access, sql server, oracle, sybase, mysql, quadbase etc.,]

    the tests performed on these applications would be
    1. User interface testing
    2. Manual support testing
    3. Functionality testing
    4. Compatability testing
    5. Intersystems testing

    Desktop:
    01. Application runs in single memory (Front end and Back end in one place)
    02. Single user only

    Client/Server:
    01. Application runs in two or more machines
    02. Application is a menu-driven
    03. Connected mode (connection exists always until logout)
    04. Limited number of users
    05. Less number of network issues when compared to web app.

    Web:
    01. Application runs in two or more machines
    02. URL-driven
    03. Disconnected mode (state less)
    04. Unlimited number of users
    05. Many issues like hardware compatibility, browser compatibility, version compatibility, security issues, performance issues, etc
    see friend when we consider the security testing, both application should well secured to internal and external threat.

    As per difference in both the applications come where, how to access the resources. In client server once connection is made it will be in state on connected, whereas in case of web testing http protocol is stateless, then there comes logic of cookies, which is not in client server.

    More for client server users are well known, whereas for web any user can login and access the content, he/she will use it as per his intentions.

    so, there are always issuses of security and compatibility for web application.

    Regards,
    Vijay

    #103 Ranjith kumar on 05.08.08 at 11:15 am

    This one very useful to me.it’s nice one

    Thanks for details.

    #104 nodeen on 05.28.08 at 9:03 am

    how to do load testing manually? without any testing tools? is it possible?can anybody give sample of the testcases ?
    thanks.

    #105 nityasri on 06.12.08 at 3:19 pm

    hi
    thnks for providing useful info on web testing. its really nice.
    can anybody explain web testing wit a simple example?

    thx

    #106 shainaz on 07.01.08 at 8:12 am

    nice article i got lots of information from this article

    #107 shainaz on 07.01.08 at 8:17 am

    very nice article………….

    Leave a Comment