Thread: web testing

can anybody explain what is WEB TEST?

NOTE : [This question was asked by krishna]

Friends
Web Testing:-> Is nothing but testing for the application that's going to run on the web(Internet).And That Might covers all of that kind of issues.

1.Functionality
2.Stress
3.Load Testing
4.Link Coverage/Navigation
5.Contents/Data to be displayed or send to data base

Thnx & Regards
rajeev sharma

Hi team,

I would like to add up this information

understanding web tests

a web test, also called a declarative web test, consists of a series of http requests. Web tests work at the protocol layer by issuing http requests. Web tests do not run javascript. However, you can simulate javascript actions at runtime by using web test plug-ins, web test request plug-ins, extraction rules, or coded web tests. Web tests are used to test the functionality of web applications and to test web applications under load. Web tests are used both in performance tests and stress tests.

You can create web tests by recording your activities in a browser session. You can also build web tests manually by using the web test editor. To test web applications, you create web tests by recording a test that navigates through a web application.

Web test benefits you can create web tests for use in an extensive set of testing purposes:

☆create functional tests that exercise your web applications.
☆create data-driven tests.
☆create and run tests that can test the performance of your applications. ☆use .net languages for test authoring, debugging, and test extensibility.

Web tests automatically handle these aspects of http:

☆hidden field correlation including viewstate
☆redirects
☆dependent requests
☆authentication
☆security through https/ssl by using the web test viewer, you can view and debug your web tests for verification.

For more information, see how to: run a web test. Coded web tests a web test starts as a list of urls, representing web requests, in the web test editor. If necessary, these requests can be converted to visual c# or visual basic code, called a coded web test. After a web test has been converted to its coded format, looping and branching constructs can be added.

For more information about how to create a coded web test, see how to: create a coded web test. Considerations for load testing web tests, although useful by themselves, are also used in load tests. Load tests allow you to aggregate several web tests that simulate a real user load on your web site. Before you can exercise the load test functionality, you must first create a web test or several web tests.

You can set properties on load tests that broadly apply to the individual web tests. You can combine web tests with unit tests in a load test, when appropriate in your test plans. For more information about load tests, see working with load tests.

Security web tests and web test results contain potentially sensitive information that could be used to build an attack against a computer or network. Web tests and web test results contain urls and connection strings. You should be aware of this when you share tests or test results with others.

Regards,
Sridevi

Actually i need your help regarding testing line.
I m working in a small concern in which in am working as a tester & i am doing static testing the website made in either PHP or dotnet but i am not using the tool & here i am not working under any QA.As i am the only person who is doing testing the sites & no body is there from whom i get the experience. I simply create a report on excel sheet & give to developers for fixing & then i verify it..

Tell me is this the right experience???

As i passed my B.tech in 2004 & i did worked here for past 1 year on the same platform..

Please help me how could i apply for betterment..
& how could i move higher in this field ....

I think you are the right person who will definately help me regarding that....

Thanks

Originally Posted by rajeev kant sharma

friends web testing:-> is nothing but testing for the application that's going to run on the web(internet).and that might covers all of that kind of issues. 1.functionality 2.stress 3.load testing 4.link coverage/navigation 5.contents/data to be displayed or send to data base thnx & regards rajeev sharma

web testing during testing the websites the following scenarios should be considered. • functionality • performance • usability • server side interface • client side compatibility • security functionality: in testing the functionality of the web sites the following should be tested. Links internal links external links mail links broken links forms field validation functional chart error message for wrong input optional and mandatory fields database testing will be done on the database integrity. Cookies testing will be done on the client system side, on the temporary internet files. Performance: performance testing can be applied to understand the web site's scalability, or to benchmark the performance in the environment of third party products such as servers and middleware for potential purchase. Connection speed: tested over various networks like dial up, isdn etc load what is the no. Of users per time? check for peak loads & how system behaves. Large amount of data accessed by user. Stress continuous load performance of memory, cpu, file handling etc. Usability : usability testing is the process by which the human-computer interaction characteristics of a system are measured, and weaknesses are identified for correction. Usability can be defined as the degree to which a given piece of software assists the person sitting at the keyboard to accomplish a task, as opposed to becoming an additional impediment to such accomplishment. The broad goal of usable systems is often assessed using several criteria: • ease of learning • navigation • subjective user satisfaction • general appearance server side interface: in web testing the server side interface should be tested. This is done by verify that communication is done properly. Compatibility of server with software, hardware, network and database should be tested. The client side compatibility is also tested in various platforms, using various browsers etc. Security: the primary reason for testing the security of an web is to identify potential vulnerabilities and subsequently repair them. The following types of testing are described in this section: • network scanning • vulnerability scanning • password cracking • log review • integrity checkers • virus detection

Hi! friends

Web test is the test performed on the applications meant for internet or the world wide web.

The Tests to be applied under web testing :
- user interface testing
- functionality testing
- manual support testing
- security testing
- compatability testing
- load and stress testing
- interoperability testing / intersystems testing
- storage and data volume testing

Testing plays a critical role in the development of your web site and its long-term maintenance. Web testing is a collection of related activities with a single goal to uncover errors in web content, function, usability, navigability, performance, capacity, and security.While smaller web sites— especially those with more limited budgets—may not need to follow the formal testing procedures that are required for large-scale, commercial web sites, every site needs to be thoroughly tested to ensure that it's error-free, user-friendly, accessible, and standards compliant.

Testing should be completed during each phase of a site's development. Testing during production makes it easier to locate and resolve errors, and minimizes the chance of existing bugs being replicated throughout later stages of development.

Hi Newhere,

testing web-based applicaiton would involve 2 aspects. Your answer for such a question should be - Yes I have tested web-based applications stressing more on on client-side aspects.

Manual testing web-based applications would involve testing the application apart from functional testing. Some of the checks like whether -

1) Home page is properly displayed with site-map and necessary links to log in and further navigate the application
2) Checking whether successful login redirects you to the next landing page
3) checking if all specified links in the web-apps are working fine
4) No Broken links
5) No Linked up pages or circular links
6) Home page link is provided on all pages etc.

Incase we are automating a web-apps, we could still carry out the above checks using PageCheckpoints, counting the number of links etc.....

Cheers.....

Bizzzzzare

Originally Posted by newhere

Hi guys
I am new in testing never worked in any company. I just completed my testing course and now i am preparing for the interview. One of my friend was asked in interview:

"have you tested web application and how?"

Can you please give my good answer of this Q with example?

Hi

Web Application testing is nothing but an application which would be used on internet.

Testing of the functionality/hyperlinks/buttons etc..

Eg:Yahoo mail.

Checking the functionality of "inbox" "sent items" deleted items...etc...
Images: If image has some link....click on that It should go to the particular page or required page....

This is basic idea.....

Regards
Suneel

Hi Guys i m just new in testing. And i want to know how can we do web testing?
If some one ask you "have you done webtesting and how did you do that explain me with an example" Then what will be the best answer?

Hi Newhere,

Web testing on the first look seems to be simply testing the functionality of a web-application. Other than Functional testing of the applicatio, web-testing would cover -
1) Checking that the Web Pages get loaded completely.
2) Navigational flow between web-pages happens exactly as specified in FRS
3) Check for Broken links
4) check non-existence on non-circular links
5) Basic checks like existence of Home Page link at every page, siteMap, Logout option etc

This is doing a Manual testing of the Web-application as such.

A few points of the above can be implemented in Automated Functional testing as well using Page Checkpoints and a few standard checkpoints.

Now apart from this basic tests, a web-page can also be tested for Performance. Here we would be testing the Page Loading time, response times between requests (Navigation from One State of application to another) etc. This is called as Performance Testing.

We could also test a web-application for Security Testing. In this case we try to breach the authentication protocols, proxy servers etc being used by the web-application. We have different security testing techinques like SQL Injection, Broken Access Link, Man-in the Middle etc.

We could also perform a Netowrk test on a Web-applicaiton where we check the connecivity between the different servers being used by the Web-application. In sense, the data flow from AppServer through Web-Server to finally the DB Server.

Hence a chic and proper answer would be -

"A Web Application apart from being tested Functionally and Basic checks, can also be Performance Tested, Security Tested and Network Tested."

Cheers.....

Hi Bizzzzzzare

Thanks a lot man. You are gr8t. I completely understand.

ad hoc testing is an unplanned testinng of a perticular
issue or issues. When ever a requiest comes test team has
to manage the resource to perform the task and plan the
delivarables as commited.

Basically a Web Application is also a Client server application where someone sends requests (browser, interface, webpage etc.) and someone gives response (DB Server etc).

Hello to all,

I am currently working as a tester since 7 months. Mainly i have test the web applications in my company. I am testing web sites like some changes need to done over there and after changes have been done i have to testing of the particular changes. So, i am doing this without using any test tool. I did not use any test tool yet.

I want to know that in testing line that what testing i am doing. Should i use any test tool? OR we can not test a web application (web sites) without using any test tool?

Please give me reasonable ans.

Thanks in advance,

hi jyothi,

You need a test tool like QTP where you can build reusable functions and when ever the change is made by the developer you need to check it again. If you test manually it will take time for an hour or two hours if you use testing tool it can be done with in 10 minutes. Here the task is also completed and we are also saving our time. Use QTP it is a best tool for companies perspective.

Thanks
Deepasree

Thanks Deepasree.

The first part ("I am testing web sites like some changes need to done over there ") might not be possible to automate depending on what your testing to decide whether something has to be changed or not (e.g. are you testing if certain functionality doesn't work or if requirements aren't fullfilled?) If it is just about the functionality automating it is no problem.

The second part ("after changes have been done i have to testing of the particular changes") is called regression testing which is automated in general.

Note: depending on the extend of changes your application is undergoing you have to see whether automation requires too much effort to maintain