Testing Definitions

Ad-hoc Testing:
It is done without any formal test plans and test cases. Tester should have a significant understanding of software before testing it. It is normally done by experienced tester who has got good knowledge of software to be tested.
This testing is also done where software has to be tested in a very less time constraint.

Exploratory Testing:
It is done by the tester who has got less or no knowledge about the software which they are going to test. They can use this testing to write test cases. This is done at the initial stage of testing. This is majorly done to know the flow of software.

Negative Testing:
Negative testing is testing the tool with improper inputs. Negative Testing is simple testing the application beyond and below of its limits. For ex:
1) We want to enter a name for that negative test can be first we enter numbers.
2) We enter some ASCII characters and we will check
3) First numbers and characters we will check
4) Name should have some minimum length below that we will check

Load Testing:
Analyze number of things in load testing few:

1. Response times - Do they appear consistent, or is there any degrade over a period of time/Are they higher than what is expected
2. Performance of the hardware components – Mid-tier server or the application server, http server, and the database server. The CPU utilization, JVM memory heap of the application server, and the CPU of database server are important for assessing the performance.

Software Integration Environment (SIT):
This includes:
a. Server Machine
b. Database Machine
c. Client Machine

In real world scenario, application is tested using different machines for performance and compatibility purposes.

Database Testing:
In DB testing we need to check for,

1. The field size validation.
2. Check constraints.
3. Indexes are done or not (for performance related issues)
4. Stored procedures
5. The field size defined in the application is matching with that in the db.