Web Testing Vs GUI testing
Hey every one, I don't contain a bundle of description to Web based testing as a good number of the occasion I was concerned through GUI bottom testing.....
Currently my Question is that what are out of the ordinary thoughts that I have to be supposed to give are while Web testing.
How it is dissimilar from GUI based testing??
Thankfulness in move forward
Last edited by amit002; 10-24-2013 at 08:34 AM.
Was this an interview question?
I think the two terms are very similar. I'm wondering what lead to the question.
As Kevin said, both Web testing and UI testing reflects same purpose. You have to perform the functionality, URL, Content, UI functions etc tests.
GUI testing is the part of web testing as well as desktop testing. In GUI testing we check the graphical user interface that is Font size, font colour, links, labels etc.
GUI testing is part of Web testing as well as Desktop testing.
GUI testing is one type of Non-Functional testing which contains testing of all user interfaces, color, font, style through the application, header,footer, all alert messages, spell , grammar, user friendllyness, compatibility with all other browsers.
Do let me know if you need any further help
GUI testing is the piece of web testing and in addition desktop testing
In GUI testing we check the graphical client interface that is Font size, text style shading, joins, marks and so forth.
Webtesting implies it is a 3 level engineering, here we check the execution of the application (volume, load, stress). Here we do the compactability testing, client interface testing and so forth.
Convert TestComplete Web tests into performance tests to reduce test creation time.
To generate a set of test cases, test designers attempt to cover all the functionality of the system and fully exercise the GUI itself. The difficulty in accomplishing this task is twofold: to deal with domain size and with sequences. In addition, the tester faces more difficulty when they have to do regression testing. Unlike a CLI (command line interface) system, a GUI has many operations that need to be tested. A relatively small program such as Microsoft WordPad has 325 possible GUI operations. In a large program, the number of operations can easily be an order of magnitude larger. The second problem is the sequencing problem. Some functionality of the system may only be accomplished with a sequence of GUI events. For example, to open a file a user may have to first click on the File Menu, then select the Open operation, use a dialog box to specify the file name, and focus the application on the newly opened window. Increasing the number of possible operations increases the sequencing problem exponentially. This can become a serious issue when the tester is creating test cases manually.
Regression testing becomes a problem with GUI's as well. A GUI may change significantly, even though the underlying application does not. A test designed to follow a certain path through the GUI may then fail since a button, menu item, or dialog may have changed location or appearance. These issues have driven the GUI testing problem domain towards automation. Many different techniques have been proposed to automatically generate test suites that are complete and that simulate user behavior. Most of the testing techniques attempt to build on those previously used to test CLI (Command Line Interface) programs, but these can have scaling problems when applied to GUI’s. For example, Finite State Machine-based modeling — where a system is modeled as a finite state machine and a program is used to generate test cases that exercise all states — can work well on a system that has a limited number of states but may become overly complex and unwieldy for a GUI .
Web testing is the name given to software testing that focuses on web applications. Complete testing of a web-based system before going live can help address issues before the system is revealed to the public. Issues such as the security of the web application, the basic functionality of the site, its accessibility to handicapped users and fully able users, its ability to adapt to the multitude of desktops, devices, and operating systems, as well as readiness for expected traffic and number of users and the ability to survive a massive spike in user traffic, both of which are related to load testing. A web application performance tool (WAPT) is used to test web applications and web related interfaces. These tools are used for performance, load and stress testing of web applications, web sites, web API, web servers and other web interfaces. WAPT tends to simulate virtual users which will repeat either recorded URLs or specified URL and allows the users to specify number of times or iterations that the virtual users will have to repeat the recorded URLs. By doing so, the tool is useful to check for bottleneck and performance leakage in the website or web application being tested.
A WAPT faces various challenges during testing and should be able to conduct tests for:
Operating System compatibility
Windows application compatibility where required
WAPT allows a user to specify how virtual users are involved in the testing environment.ie either increasing users or constant users or periodic users load. Increasing user load, step by step is called RAMP where virtual users are increased from 0 to hundreds. Constant user load maintains specified user load at all time. Periodic user load tends to increase and decrease the user load from time to time.
Web security testing tells us whether Web based applications requirements are met when they are subjected to malicious input data. There is a web application security testing plug-in collection for FireFox
Thanks and Regards
Software Test Engineer
GUI testing s conducted for both web and desktop applications. GUI testing mainly comprises of validating UI controls. Web testing usually contains below specific testing
- Compatibility Testing
- Security Testing
- Load testing
- Volume testing
Web Testing is more complex thing as it assumes the following:
- Web Testing is more "protocol-based" you need to mind that any action leads to the relevant HTTP request
- You need to mind browser specifics, i.e. cookies, cache, images, styles
- Desktop applicaiton is used by one person while Web application has a backend which can be used by lots of people so you need to consider Load, Stress and Soak testing as well
Tags for this Thread