How to Perform Web Testing

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 session’s 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 crawl able 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.

QTP INTERVIEW QUESTIONS

1. How to create basic scripts from a manual test case in QTP?
2. How to add verification steps to tests?
3. How to use custom checkpoints in QuickTest Professional?
4. How to use database checkpoints?
5. How to manage objects in the Object Repository in QuickTest Professional?
6. How to parameterize tests?
7. How to customize checkpoints with parameters?
8. How to run an integrated test scenario using Multiple Actions?
9. How to use the QTP Step Generator?
10. How to use debug tools?
11. How to create virtual objects?
12. What is the difference between QTP Analog and Low-Level recording
modes?
13. Please describe Object and Smart Identification?
14. What is the difference between Per-Action vs. Shared Object Repositories?


Questions on Basics of the QTP functionality:


1. What are the main benefits of QuickTest Professional?
2. What is Add-In Manager in QTP?
3. What QTP Options do you know?
4. How to Identify Objects and their Properties?
5. What is the Object Repository?
6. How to Add Synchronization Steps?
7. How to Set the Global Sync Timeouts in QTP?
8. What is Regular Expressions and how to use them?
9. How to Create Data-Driven tests?
10. What are Checkpoints with Parameters?
11. What is the difference between Global and Local Data Sheets?
12. How to create Reusable and Multiple Actions?
13. Describe the benefits of the Step Generator.
14. What are the main options that are available in the Step Generator dialog
box?
15. What is Exception Handling?
16. What is Recovery Scenario Wizard in QTP?
17. Describe the purpose of a Database Checkpoint
18. What is the difference between Analog Recording and Low-Level Recording
in automation tools?
19. Describe Per-Action vs. Shared Object Repositories
20. Describe how and when Smart Identification is used

BUG LIFECYCLE

SOFTWARE TESTING Interview questions

1. What is Software Testing?
Ans. Testing involves operation of a system or application under controlled
conditions and evaluating the results. The controlled conditions should include
both normal and abnormal conditions.
Testing is a process of executing a program with the intend of finding the
errors.

2. What is the Purpose of Testing?
Ans. The purpose of testing is
1· To uncover hidden errors
2· To achieve the maximum usability of the system
3· To Demonstrate expected performance of the system

3. What types of testing do testers perform?
Ans. Two types of testing 1.White Box Testing 2.Black Box Testing.

4. What is the Outcome of Testing?
Ans. The outcome of testing will be a stable application which meets the customer
Req's.

5. What kind of testing have you done?
Ans. Usability, Functionality, System testing, regression testing, UAT
(it depends on the person).

6. What is the need for testing?
Ans. The Primary need is to match requirements get satisfied with the
functionality
and also to answer two questions
1· Whether the system is doing what it supposes to do?
2· Whether the system is not performing what it is not suppose to do?

7. What are the entry criteria for Functionality and Performance testing?
Ans. Entry criteria for Functionality testing is Functional Specification /BRS
(CRS)/User Manual. An integrated application, Stable for testing.
Entry criteria for Performance testing is successfully of functional testing,
once all the requirements related to functional are covered and tested, and
approved or validated.

8. What is test metrics?
A. The objective of Test Metrics is to capture the planned and actual quantities the effort, time and resources required to complete all the phases of Testing of the SW Project.

9. Why do you go for White box testing, when Black box testing is available?
A. A benchmark that certifies Commercial (Business) aspects and also functional
(technical) aspects is objectives of black box testing. Here loops, structures,
arrays, conditions, files, etc are very micro level but they arc Basement for
any application, So White box takes these things in Macro level and test these
things Even though Black box testing is available, we should go for White box testing
also, to check the correctness of code and for integrating the modules.

10. What are the entry criteria for Automation testing?
A. Application should be stable. Clear Design and Flow of the application is
needed.

11. When to start and Stop Testing?
A. This can be difficult to determine. Many modern software applications are so
complex, and run in such an interdependent environment, that complete testing
can never be done.

Common factors in deciding when to stop are:
Deadlines (release deadlines, testing deadlines, etc.)
Test cases completed with certain percentage passed
Test budget depleted
Coverage of code/functionality/requirements reaches a specified point
Bug rate falls below a certain level
Beta or alpha testing period ends

12.What is Quality?
A. It ensures that software is a Bug free, delivered in time, within budget,
meets customer requirements and maintainable. Quality standards are different
in various areas like accounting department might define quality in terms of
Profit.

13. What is Baseline document?
A. The review and approved document is called as baseline document (i.e.) Test
plan, SRS.

14. What is verification?
A. To check whether we are developing the right product according to the
customer requirements r not .It is a static process.

15. What is validation?
A. To check whether we have developed the product according to the customer
requirements r not. It is a Dynamic process.

16. What is quality assurance?
A. Quality Assurance measures the quality of processes used to create a quality
product.
1.It is a system of management activities.
2.It is a preventive process.
3.It applies for entire life cycle.
4.Deals with Process.

17.What is quality control?
A. Quality control measures the quality of a product
1.It is a specific part of the QA procedure.
2.It is a corrective process.
3.It applies for particular product.
4.Deals with the product.

18.What is SDLC and TDLC?
A. Software development life cycle(SDLC) is life cycle of a project from
starting to ending of the project.
1.Requiremnts Specification. 2.Analysis
3.Design 4.Coding
5.Testing 6.User acceptance test(UAT)
7.Maintainance
Software Test Life Cycle(STLC) is a life cycle of the testing process.
1.Requiremnts Specification. 2.Planning
3.Test case Design. 4.Execution
5.Bug Reporting. 6.Maintainance

19.What are the Qualities of a Tester?
A. Tester should have qualities like
1.ability to break 2.paitence 3.communication
4.Presentation 5.team work. 6.negative thinking with good judgment skills

20.When to start and Stop Testing?
A. repeat

21.What are the various levels of testing?
A. The various levels of testing like
1· Ad - Hoc testing
2. Sanity Test
3. Regression Testing
4. Functional testing
5· Web Testing

22.What are the types of testing you know and you experienced?
A. I am experienced in Black Box testing.

24.After completing testing, what would you deliver to the client?
A. It is depend upon what you have specified in the test plan document.
the contents delivers to the clients is nothing but Test Deliverables.
1.Test plan document 2.Master test case document 3.Test summary Report.
4.Defect Reports.

25.What is a Test Bed?
A. Test bed means under what test environment (Hardware, software set up) the
application will run smoothly.

27.Why do you go for Test Bed?
A. We will prepare test bed bcoz first we need to identify under which
environment (Hardware,software) the application will run smoothly,then
only we can run the application smoothly without any intereptions.

28.What is Severity and Priority and who will decide what?
A. Severity and priority will be assigned for a particular bug to know the
importance of the bug.
Severity:How sevierly the bug is effecting the application.
Priority:Informing to the developer which bug to be fix first.

29.Can Automation testing replace manual testing? If it so, how?
A. Yes,it can be done manually when the project is small,having more time.
we can test with minimum number of users.

30.What is a test case?
A. A test case is a document that describes an input, action, or event and an
expected response, to determine if a feature of an application is working
correctly.

31.What is a test condition?
A. The condition required to test a feature.(pre condition)

32.What is the test script?
A. Test script is the script which is generated by an automation tool while
recording a application features

33.What is the test data?
A. Test data means the input data (valid, invalid data) giving to check the
feature of an application is working correctly.

34.What is an Inconsistent bug?
A. the bug which is occurring

35.What is the difference between Re-testing and Regression testing?
A Re-testing:Executing the same test case by giving the no. of inputs on same
build.
Regression testing:Executing the same test case on a modified build.

36.What are the different types of testing techniques?
A. 1.white Box testing 2.Black Box testing.

37.What are the different types of test case techniques?
A. 1.Equilance Partition. 2.Boundary Value Analysis. 3.Error guesing.

39.Differentiate Test bed and Test Environment?
A. Both are same.

40.What ifs the difference between defect, error, bug, failure, fault?
A. Defect: While executing the test case if u found any mismatch, then u will
report it to the development team, that is called defect.
Bug: Once the developer accepts your defect, then it is called as a bug.
Error: it may be program error or syntax error.

42. What is the difference between White & Black Box Testing?
A. White Box Testing: Based on the knowledge of the internal logic of an
application's code.Tests are based on coverage of code statements, branches,
paths, conditions.
Black Box testing:- not based on any knowledge of internal design or code.
Tests are based on requirements and functionality.

43.What is the difference between Quality Assurance and Quality Control?
A. Refer Question no.16 & 17
Quality Assurance measures the quality of processes used to create a
quality product. Quality control measures the quality of the product.

44.What is the difference between Testing and debugging?
A. The Purpose of testing is to show the program has bugs.
The Purpose of debugging is find the error/ misconception that led to failure
and implement program changes that correct the error.

45.What is the difference between bug and defect?
A. Defect:While executing the test case if u found any mismatch,the u will
report it to the development team,that is called defect.

5 common problems in the software development process

• Poor requirements - if requirements are unclear, incomplete, too general, or not testable, there will be problems.
• Unrealistic schedule - if too much work is crammed in too little time, problems are inevitable.
• Inadequate testing - no one will know whether or not the program is any good until the customer complains or systems crash.
• Featuritis - requests to pile on new features after development is underway; extremely common.
• Miscommunication - if developers don't know what's needed or customer's have erroneous expectations, problems are guaranteed.

Define usecase and testcase?

UseCase :
It is indepth detailed description about Customer
Requirments. it is developed from BRS/SRS. it is prepared
by business analyst or QA Lead.

Testcase:
It is a doument describing the input,action and
expected response to determine wether the application is
working correctly according to the customer requirments.
it is derived from srs,usecases and test scenarios. while
developing test cases we can find gaps in the requirments
also.

Use case is a set of scenario's of User requirement.
Test Case is a document Designed based on the Use case
To Evaluate between Expected & Actual Result.

USE cases is a pictorial representation of requirments.
Test Case is a document Designed based on the Use case
To Evaluate between Expected & Actual Result.

Difference between User Acceptance Test cases and System Test Cases

System Testing:
Finding the defects when the system is tested as a whole this also called as end to end testing. In this testing tester needs to test the application from log-in to log-out.

User Acceptance Testing:
User acceptance testing is to get the acceptance from the client. UAT is generally done at client's environment. Before UAT pre UAT should be done.