- SailFin QL will execute SF smoke tests also.
- For changes that span multiple modules, additional tests might need to be run
- For major changes that affect SIP container, Sip Regression tests need to be run
- For any change in GlassFish, GlassFish QL need to be run
- For major changes that affect GlassFish, GlassFish CTS and GlassFish smoke need to be run
- For significant changes that might affect different modules, and if you dont know what tests need to be run, send a mail and ask dev@sailfin alias
How to Run QL tests Module wise list of tests
table-filter
| Module |
Directories in CVS |
Minimum set of Tests |
Unit Tests or Developer Tests |
Comments |
| Deployment |
SF_HOME/deployment |
QL and Cluster QL) |
Deployment developer tests (How To Run) |
For major changes GlassFish deployment tests also will be run. |
| Sip Stack |
SF_HOME/sip-stack |
QL |
Sip Stack Unit Tests (Ho To Run) |
For serious changes, module owner might decide to run Cluster QL also. |
| Admin |
SF_HOME/admin |
QL and Cluster QL |
Admin developer tests |
|
| Session Replication |
SF_HOME/replication |
QL and Cluster QL |
Replication developer tests (How To Run) |
|
| CLB |
SF_HOME/clb |
QL and Cluster QL |
LB developer tests |
|
| Integrations (Grizzly, dnsjava etc) |
SF_HOME/bootstrap |
QL and Cluster QL |
Sip Stack Unit Tests |
If the change is significant enough, please make sure that CLB, security and admin tests are run |
| Security |
SF_HOME/security |
QL |
Security developer tests |
For major changes Cluster QL and GlassFish security tests will be run |
%%
%%
|
