Welcome to the new Parasoft forums! We hope you will enjoy the site and try out some of the new features, like sharing an idea you may have for one of our products or following a category.
How do I test servlets/EJBs with Jtest?
LegacyForum
Posts: 1,664 ✭✭
Testing any and all Java components that depend on the presence of web containers or application servers can be very complex. To ensure that these components are operating properly, a three-fold testing approach is recommended.
1. While you are in development and are not yet ready to deploy the components on the server:
Use Parasoft Jtest to analyze this code-- as well as any other Java code that sits in the
source control repository. During this analysis, Jtest will find bugs that represent bad patterns throughout the code, flow dependent errors, and errors exposed by automatic unit testing. If all of these bugs and violations found by Jtest are addressed during development, the code delivered to QA will be of higher quality and free of bugs that would have been otherwise been discovered in QA or in production.
2. When you are ready to deploy on the application server, run in-container testing:
Use Parasoft Jtest to test your code as it is deployed on the server. Alternatively, you could use Jtest to monitor a running application and capture tests with the ?real data values? and ?real sequence calls? that were made. These tests can be used to verify that your code is operating according to its specification and requirements, or to help development narrow down the source of an error. They can be run against your code on a regular basis to ensure that the tested functionality remains consistent.
3. When you are ready to deploy on the application server, test the external interface: Once you are confident that your EJBs are properly implemented, you can also use Parasoft SOAtest'sEJB Client to test the remote interface of your deployed EJBs.
1. While you are in development and are not yet ready to deploy the components on the server:
Use Parasoft Jtest to analyze this code-- as well as any other Java code that sits in the
source control repository. During this analysis, Jtest will find bugs that represent bad patterns throughout the code, flow dependent errors, and errors exposed by automatic unit testing. If all of these bugs and violations found by Jtest are addressed during development, the code delivered to QA will be of higher quality and free of bugs that would have been otherwise been discovered in QA or in production.
2. When you are ready to deploy on the application server, run in-container testing:
Use Parasoft Jtest to test your code as it is deployed on the server. Alternatively, you could use Jtest to monitor a running application and capture tests with the ?real data values? and ?real sequence calls? that were made. These tests can be used to verify that your code is operating according to its specification and requirements, or to help development narrow down the source of an error. They can be run against your code on a regular basis to ensure that the tested functionality remains consistent.
3. When you are ready to deploy on the application server, test the external interface: Once you are confident that your EJBs are properly implemented, you can also use Parasoft SOAtest'sEJB Client to test the remote interface of your deployed EJBs.
0