1. WEB Testing

2. Ventsislav Ivanov Certificated QA at Telerik Academy
Automation engineer at Vermint

3. Table of Contents Web Sites vs Web App Testing Web Applications
Web Testing Types
Test Automation
Functional Web Testing
Non-functional Web Testing

4. Web Sites vs Web App

5. Web Sites
Virtual location on WWW, containing several subject or company related webpages and data files accessible through a browser. Each website has its own unique web address (see uniform resource locator) which can be reached through an internet connection. The opening page of a website is usually called homepage which contains hyperlinks to other pages on the same or other site(s). A single web server may support multiple websites and a single website may reside on multiple web servers, sometimes thousands of miles apart.

6. Web Application
An application that is usable only with an active Internet connection and that uses HTTP as its primary communications protocol. Also called web application.

7. User point of view
That certainly seems simple enough: Web sites are for consumption what Web apps are for creation. Does it sound right?

8. Developer point of view
Self-contained
Interactive user interface, possibly mimicking the native UI of the device
Using advanced device capabilities – like geo location, camera integration, or other technologies that the W3C Device APIs and Policy Working Group is developing
Action-oriented rather than information oriented
Not relying heavily on (or hiding when possible) the browser
Working off-line, for example using HTML5 ApplicationCache, localStorage, or indexed database

9. Difference in testing
If you are good enough to test Web App, it will be no problem for you to test WebSite

10. Testing Web Applications

11. Web Testing Issues
Testing a web application is quite a bit more difficult than testing the same functionality in a Windows Desktop application
Various issues are present:
Timing difficulties
Differences between browsers
New technologies that make web browsing a rich, but difficult-to-test, experience

12. Web Testing Issues
Web browsers don't provide clear visibility to what's happening on the page
The tester has no straight-forward way of consistently identifying an element on a web page and detecting changes in the element's state

13. Web Testing Issues New technologies introduce new testing issues
The same features that make web browsing a richer experience also present obstacles to testing
Asynchronous processes
Client side code running directly in the browser
Animation
Etc.

14. Web Testing Types

15. Web Testing Types Functional/Regression Testing
Load and Performance Testing
Web Site Security Testing
Web Site Management Testing
Mobile Web/App Testing

16. Web Page Functionality Test
Check all the links
the outgoing links from all the pages from specific domain under test
all internal links
links jumping on the same pages
links used to send the
check if there are any orphan pages
check for broken links

17. Web Page Functionality Test
Test forms in all pages
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

18. Web Page Functionality Test
Cookies testing
Test the application by enabling or disabling the cookies in your browser options
Test if the cookies are encrypted before they are written to user machine
Check application security by deleting the cookies

19. Web Page Functionality Test
Test HTML and CSS
Checking for syntax errors
Readable color schemas
Standard compliance
E.g. standards such W3C and ISO is followed

20. Web Page Functionality Test
Database Testing
Testing the backend databases, like comparing the actual results with expected results

21. Web Page Functionality Test
Database Testing
Database testing basically include
Data validity testing
Test if any errors are shown while executing queries
Data integrity testing
Maintained while creating, updating or deleting data in database
Check response time of queries
Test data retrieved from the database is shown accurately in the web application

22. Web Page Usability Test
A method of simulating the user's way of experience
E.g., checking help links, contents in the page, checking menu options and their links, think times between the pages and message dialogs in the pages

23. Web Page Usability Test
Test for navigation
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
Web site should be easy to use
Instructions should be provided clearly and correct (it means whether they satisfy purpose)

24. Web Page Usability Test
Content checking
Content should be logical, easy to understand and meaningful
Check for spelling errors
All the anchor text links should be working properly
Images should be placed properly with proper sizes

25. Interface Testing The main layers are Web server Application server
Database server
Check if all the interactions between these servers are executed properly

26. Compatibility Testing
Browser compatibility
Operating system compatibility
Mobile browsing
Printing options

27. Compatibility Testing
Testing web page compatibility
A method of testing multiple browsers based on user requirements
The web page presentation depends on how well the components are used

28. Compatibility Testing
Sample browser compatibility checklist
CSS validation
HTML or XHTML validation
Page validations with and without JavaScript enabled
Ajax and jQuery functionality
Font size validation
Page layout in different resolutions
All images and alignment
Header and footer sections
Page styles
Date formats
Special characters with HTML character encoding
Page zoom-in and zoom-out functionality

29. Security Testing Testing for vulnerabilities of the web application
Test unauthorized access to secure pages should not be permitted
Restricted files should not be downloadable without appropriate access
Check sessions are automatically killed after prolonged user inactivity

30. Performance Testing
Verifies web page responses as per expectations based on the environment
Also includes stress testing and load testing of the application

31. Performance Testing Testing a web application using different networks
Required due to different points a user may access the system from
E.g., a local intranet or an internet with a lower network speed
An application's performance and the accessibility are based directly on the network used
This is also part of performance testing

32. Test Environment
Set up a test environment that is separate from your development and production environment
This includes a separate web server, database server, and application server if applicable

33. Test Environment
There are many other types of testing that can be performed as part of Web Performance Testing:
Using different operating systems
Using different databases
Installing different versions of an operating system

34. Test Automation

35. Automated Defect Prevention: Best Practices in Software Management
Test Automation
Test Automation is the use of special software (separate from the software being tested) to control the execution of tests and the comparison of actual outcomes with predicted outcomes.
Automated Defect Prevention: Best Practices in Software Management

36. Test Automation
Test automation is critical for continuous delivery and continuous testing.

37. Level and types of tests that can be automated
Levels
Types
Unit testing
Integration testing
System testing
Functional Testing
Non-Functional Testing
Black Box Testing
Smoke Testing
Regression Testing
Data Driven Testing
Keyword Testing

38. Test automation tools Unit tests tools
C# - Nunit, MbUnit, MSTest, xUnit.net
Java – JUnit, JTest, Arquillian, TestNG
JavaScript – JSLint, Qunit, SugarTest
Python –  doctest, unittest, pytest
Ruby – Minitest, Rspec, Bacon

39. Test automation tools Integration test tools
Component integration testing
Expose defects in the interfaces and interaction between integrated components
Also called
“Integration test in the small”
System integration testing
Testing the integration of systems and packages
Testing interfaces to external organizations
“Integration test in the large”

40. Test automation tools System functional test tools
Graphical User Interface (GUI) testing
Selenium Web Driver
Sikuli
API driven testing
SoapUI
HttpMaster
Parasoft
vREST

41. Selenium Web Driver
Live Demo

42. Non-functional testing
Performace
Load
Endurance
Stress
Spike

43. Performace test
Determines or validates the speed, scalability, and/or stability characteristics of the system
It is also the superset of other classes of performance-related testing
The goal of performance testing is not to find bugs, but to:
Eliminate bottlenecks
Establish a baseline for future regression testing
Determine compliance with performance goals and requirements

44. Performace test metrics
A variety of performance testing metrics is used in practice:
Requests Per Second
Bytes Per Second
Latency
Maximum Concurrency

45. Performace test Myths
Client server performance problems can usually be fixed by simply plugging in a more powerful processor.
If features work correctly, users do not mind a somewhat slow response.
No elaborate plans are required for testing; it is intuitively obvious how to measure the system’s performance.
Needs just a few hours to check performance before deployment.
PT does not require expensive tools.
Anyone can measure and analyze the performance; it does not require any specialized skills.

46. Visual Studio Test Performace Testing
Live Demo

47. QUESTIONS?