Database Testing.

To test the database:

• Create a controlled version of the migrated database.
• Oracle recommends that you keep the database migration scripts in a source control system.
• Design a set of test cases that you can use to test the Oracle database from unit to system level. The test cases should:

Ensure the following:

• All the users in the source database have migrated successfully.
• Privileges and grants for users are correct.
• Tables have the correct structure, defaults are functioning correctly, and errors did not occur during mapping or generation.

Validate that the data migrated successfully by doing the following:

• Comparing the number of rows in the Oracle database with those in the source database.
• Calculating the sum of numerical columns in the Oracle database and compare with those in the source database.

Ensure that the following applies to constraints:

• You cannot enter duplicate primary keys.
• Foreign keys prevent you from entering inconsistent data.
• Check constraints prevent you from entering invalid data.
• Check that indexes and sequences are created successfully.

Ensure that views migrated successfully by doing the following:

• Comparing the number of rows in the Oracle database with those in the source database.
• Calculating the sum of numerical columns in the Oracle database and compare with those in the source database.

Ensure that triggers, procedures, and functions are migrated successfully. Check that the correct values are returned for triggers and functions.

Data integrity is tested by the following tests: Verify that you can create, modify, and delete any data in tables. Verify that sets of radio buttons represent fixed sets of values. Verify that a blank value can be retrieved from the database. Verify that, when a particular set of data is saved to the database, each value gets saved fully, and the truncation of strings and rounding of numeric values do not occur. Verify that the default values are saved in the database, if the user input is not specified. Verify compatibility with old data, old hardware, versions of operating systems, and interfaces with other software.

Cookie Testing

What is Cookie?

• Cookie is small information stored in text file on user’s hard drive by web server. 
• It is usually a small piece of data sent from a website and stored in a user's web browser while a user is browsing a website. 
• When the user browses the same website in the future, the data stored in the cookie can be retrieved by the website to notify the website of the user's previous activity.

Cookie Testing Test Cases

• Check if the application is writing cookies properly or not.
• Test to make sure that no personal or sensitive data is stored in the cookie. If it is there in cookies, it should be in encrypted format.
• If the application under test is a public website, there should not be overuse of cookies. It may result in loss of website traffic if browser is prompting for cookies more often.
• Close all browsers, delete all previously written cookies and disable the cookies from your browser settings. Navigate or use that part of web site which use cookies. It should display appropriate messages like "For smooth functioning of this site please enable cookies on your browser."
• Set browser options to prompt whenever cookie is being stored / saved in your system. Navigate or use that part of web site which use cookies. It will prompt and ask if you want to accept or reject the cookie. Application under test should display an appropriate message if you reject the cookies. Also, check that if pages are getting crashed or data is getting corrupted.
• Close all browsers windows and manually delete all cookies. Navigate various web pages and check and see if these web pages show unexpected behavior.
• Edit few cookies manually in notepad or some other editor. Make modifications like alter the cookie content, name of the cookie, change expiry date etc. Now, test the site functionality. Corrupted cookies should not allow to read the data inside it.
• Cookies written by one web site should not be accessible by other website.
• If you are testing an online shopping portal, Check if reaching to your final order summary page deletes the cookie of previous page of shopping cart properly and no invalid action or purchase got executed from same logged in user.
• Check if the application under test is writing the cookies properly on different browsers as intended and site works properly using these cookies. This test can be done on browsers like different versions of internet explorer, Mozilla Firefox, Netscape, Opera etc.
• If the application under test is using cookies to maintain the logging state for users. Check if some id is being displayed in the address bar. Now, change the id & press enter. It should display an access denied message and you should not be able to see other user's account.

What is Web Testing?

• 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, 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.

Web security testing

• Web security testing tells us whether Web based applications requirements are met when they are subjected to malicious input data.

Web Testing Checklist

• Functionality Testing
• Link Testing
• Form Testing
• Cookie Testing
• HTML/CSS Validation
• Database Testing
• Usability testing
• Navigation Checking
• Content Checking
• Interface testing
• Web server and application server interface
• Application server and Database server interface.
• Compatibility testing
• Browser compatibility
• Operating system compatibility
• Mobile browsing
• Printing options
• Performance testing
• Load Testing
• Stress Testing
• Security testing
• URL Manipulation
• Session Testing
• SQL Injection
• Cross Site Scripting
• Vulnerability Testing
• Password Cracking
• Spoofing

For Complete Web Application Checklist, Please visit the below link: http://softwaretestingreference.blogspot.in/p/web-application-testing.html

What is Ad Hoc Testing?

• Ad hoc testing is a commonly used term for software testing performed without planning and documentation. 
• The tests are intended to be run only once, unless a defect is discovered. Ad hoc testing is the least formal test method. As such, it has been criticized because it is not structured and hence defects found using this method may be harder to reproduce (since there are no written test cases). 
• However, the strength of ad hoc testing is that important defects can be found quickly.
• It is performed by improvisation: the tester seeks to find bugs by any means that seem appropriate. 
• Ad hoc testing can be seen as a light version of error guessing, which itself is a light version of exploratory testing

What is Performance Testing?

• Performance testing is a testing performed to determine how a system performs in terms of responsiveness and stability under a particular workload. 
• It can also serve to investigate, measure, validate or verify other quality attributes of the system, such as scalability, reliability and resource usage.
• Performance testing is a means of quality assurance (QA). It involves testing software applications to ensure they will perform well under their expected workload.
• The goal of performance testing is not to find bugs but to eliminate performance bottlenecks
• The focus of Performance testing is checking a software program’s
• Speed – Determines whether the application responds quickly
• Scalability – Determines maximum user load the software application can handle.
• Stability – Determines if the application is stable under varying loads

Types of performance testing.

• Load testing – Load testing is the simplest form of performance testing. A load test is usually conducted to understand the behavior of the system under a specific expected load.
• Stress testing – involves testing an application under extreme workloads to see how it handles high traffic or data processing .The objective is to identify breaking point of an application.
• Endurance testing – is done to make sure the software can handle the expected load over a long period of time.
• Spike testing – Spike testing is done by suddenly increasing the number of, or load generated by, users by a very large amount and observing the behaviour of the system. The goal is to determine whether performance will suffer, the system will fail, or it will be able to handle dramatic changes in load.
• Volume testing – Under Volume Testing large no. of. Data is populated in database and the overall software system’s behavior is monitored. The objective is to check software application’s performance under varying database volumes.
• Scalability testing – The objective of scalability testing is to determine the software application’s effectiveness in “scaling up” to support an increase in user load. It helps plan capacity addition to your software system.
• Configuration testing - Rather than testing for performance from the perspective of load, tests are created to determine the effects of configuration changes to the system's components on the system's performance and behaviour. A common example would be experimenting with different methods of load-balancing.
• Isolation testing - Isolation testing is not unique to performance testing but a term used to describe repeating a test execution that resulted in a system problem. Often used to isolate and confirm the fault domain.

Manual Testing and Automation Testing.

Manual testing

• Manual testing is the process of manually testing software for defects. 
• It requires a tester to play the role of an end user, and use most of all features of the application to ensure correct behavior. 
• To ensure completeness of testing, the tester often follows a written test plan that leads them through a set of important test cases.
• Manual testing is a laborious activity that requires the tester to possess a certain set of qualities; to be patient, observant, speculative, creative, innovative, open-minded, resourceful, unopinionated, and skillful.

Automation Testing

• Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.
• Commonly, test automation involves automating a manual process already in place that uses a formalized testing process.
• Test automation is the process of writing a computer program to do testing that would otherwise need to be done manually. 
• Once tests have been automated, they can be run quickly and repeatedly. 
• This is often the most cost effective method for software products that have a long maintenance life, because even minor patches over the lifetime of the application can cause features to break which were working at an earlier point in time.

What is Security testing?

• Security testing is a process to determine that an information system protects data and maintains functionality as intended.
• The six basic security concepts that need to be covered by security testing are: confidentiality, integrity, authentication, availability, authorization and non-repudiation. 
• Security testing is related to the security of data and the functionality of the application. You should be aware of the following concepts while performing security testing:
• Confidentiality - The application should only provide the data to the relevant party e.g. one customer's transactional data should not be visible to another customer; the irrelevant personal details of the customer should not be visible to the administrator and so on.
• Integrity - The data stored and displayed by the application should be correct e.g. after a withdrawal, the customer's account should be debited by the correct amount.
• Authentication - It should be possible to attribute the data transmitted in the application to either the application or the customer. In other words, no one other than the customer or the bank should be able to create or modify any data.
• Authorization - The application or a user should only be able to perform the tasks which they are respectively authorized to perform e.g. a customer should not be able to withdraw more than the balance in their account without having an overdraft facility, the application should not be able to levy charges on a customer account without prior customer approval.
• Availability - The data and functionality should be available to the users throughout the working period e.g. if the bank's operating times are from 8 a.m. to 8 p.m. on all working days, it should be possible for a customer to access their account and make the necessary transactions on their account.
• Non-repudiation - At a later date, it should not be possible for a party to deny that a particular transaction or data change took place e.g. if a customer withdraws an amount from their account, this should trigger the relevant actions (posting to their transaction records, debiting their account and sending them a notification etc.).