Monkey Testing:-
Testing the application by performing Abnormal actions like
1) Continuously click on any field for a long period of time and check whether the application is throwing an error or not?
2) Enter the invalid data likes tags in the application and check whether the application is crashing or not?

Exploratory Testing:-
The domain experts will perform testing on the application. While testing they will explore new requirements to provide more user-friendliness to the application.
Domains are Banking, Insurance, Telecom, Airlines, etc…etc…

Ex:————–

End to End Testing:-
Test Engineer has to identify the End-to-End scenarios, which means how the end-user is going to use the application Those kinds of scenarios are known as end-to-end scenarios.

The test engineer will execute all the end-to-end scenarios in the application check whether the application is fulfilling the end-user requirements or not is known as end-to-end testing.

Example:-

Installation / Deployment Testing:-
Deployment engineers will deploy the application in multiple environments like Dev, Testing, Stage, Production/Live, etc… and check whether the application is properly deployed or not?

Compatibility Testing: –
The test engineer will test the application in multiple environments and check whether the application is compatible in all the environments it is known as compatibility testing. This kind of testing is useful for an internet-based application like Facebook, Gmail, Irctc…

Environment Testing:-

OS + Browser:
Windows: IE, Firefox, Chrome, Safari, and Opera.
Mac: Safari, Firefox, Chrome, Opera
Linux: Chrome, Firefox, Safari, Opera
Tab: Chrome, Firefox
Mobile :
Android – Chrome, Firefox
IOS – Safari, Chrome

Authentication Testing:-
The process of checking the application with multiple sets of login credentials and check that whether the application is properly authenticating all the login credentials or not?

If it is valid it should be navigating the home page, if it is invalid the application has to provide the proper authentication message.

Direct URL Testing:-
The test engineer will take the URL of a secured page and access it in a new browser or new window in the same browser, if it is accessible the application is not secure.
If it is not accessible, then we can conclude that the application is secure.

Firewall Leakage Testing:-
Test Engineer will log in into the application as one level of user and try to access data that is above his limit and check that whether the firewall is blocking it properly or not is known as firewall leakage testing.

Whenever the build is released the testing team (Deployment team) will deploy the build-in test environment then the testing will be performed in the below order.

Build Released à Testing Team à Deploy the Build à
1) Sanity Testing
2) Test cases Execution
3) Integration Testing
4) Regression Testing
5) Re Testing
6) End to End Testing
7) Usability Testing
8) Ad hoc Testing
9) Expletory Testing
10) GUI Testing
11) Compatibility Testing


Note:
If the application is a secured application for example banking then we have to perform the below 3 tests also.
1) Authentication Testing
2) Direct URL Testing
3) Firewall Leakage Testing.

Globalization Testing:-
It is two types
1) Localization or L10N
2) Internalization / I 18N

1) Localization or L10N
Test Engineer will test the application in all the local languages like Hindi, Bengali, Telugu, Tamil, Kannada…..Etc…
And check whether the application is working as expected or not?
Localization testing supports a maximum of 10 languages and we called as L10N Testing.

2) Internalization / I 18N
Test Engineer will test the application in all the International Languages like Japanese, Chinese, French, Etc.. and Check whether it is working expected or not?

Its supports a maximum of 18 Languages hence we called
I18N Testing.