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 does Jtest work across a team?
Options
LegacyForum
Posts: 1,664 ✭✭
Jtest is a fully team-oriented Java development solution.
The optimal Jtest team configuration is to have one Jtest Server Edition on the team build machine, a Professional Edition of Jtest on every developer workstation, one Jtest Architect Edition on the architect's machine, and one installation of Team Configuration Manager on the team build machine or another team machine.
Developers use their local installations of Jtest Professional Edition to test the code that they write or modify, make the necessary corrections, then check the code in to source control. Every night, Jtest Server Edition runs on the team's build machine or another team server machine, generates additional test cases as needed, and verifies the code that all developers have checked in. After the test completes, team developers can import test result into the Jtest GUI to facilitate error examination and correction. Additionally, Jtest emails each developer an HTML report that contains only the errors/results related to his or her work, emails group managers an HTML report that lists all team/project errors and identifies which developer is responsible for each error, and uploads HTML and XML reports to Team Configuration Manager.
Throughout the process, Team Configuration Manager manages the sharing and updating of test settings and test files; this standardizes tests across the team and helps team members leverage one another's work. The standardized test settings and custom team rules are configured and maintained by the team architect, who is using Jtest Architect edition.
Jtest provides the team a rich reporting capability. It accurately identifies which developer is responsible for each error and automatically generates comprehensive reports for managers and focused reports for specific developers. Trend graphs help teams monitor how test results and code quality change over time. Goal features help teams monitor progress toward their quality goals (for instance, "No more than n coding standard violations by [date]" or "No more than n unit testing problems by [date]"). To facilitate workflow prioritization, Jtest creates a prioritized task list after every test. Moreover, Recommended Tasks functionality allows teams to restrict the number of tasks reported per developer per day; this prevents an overwhelming number of tasks from being reported at once.
To help the team leverage Jtest's findings, Jtest also integrates with the Parasoft Group Reporting System (GRS). Using the GRS dashboard and reports, a team gains unprecedented visibility into the quality, scope, and progress of their complete projects? not only their Java code, but also any related Web service functionality, Web application functionality, database functionality, and so forth.
The optimal Jtest team configuration is to have one Jtest Server Edition on the team build machine, a Professional Edition of Jtest on every developer workstation, one Jtest Architect Edition on the architect's machine, and one installation of Team Configuration Manager on the team build machine or another team machine.
Developers use their local installations of Jtest Professional Edition to test the code that they write or modify, make the necessary corrections, then check the code in to source control. Every night, Jtest Server Edition runs on the team's build machine or another team server machine, generates additional test cases as needed, and verifies the code that all developers have checked in. After the test completes, team developers can import test result into the Jtest GUI to facilitate error examination and correction. Additionally, Jtest emails each developer an HTML report that contains only the errors/results related to his or her work, emails group managers an HTML report that lists all team/project errors and identifies which developer is responsible for each error, and uploads HTML and XML reports to Team Configuration Manager.
Throughout the process, Team Configuration Manager manages the sharing and updating of test settings and test files; this standardizes tests across the team and helps team members leverage one another's work. The standardized test settings and custom team rules are configured and maintained by the team architect, who is using Jtest Architect edition.
Jtest provides the team a rich reporting capability. It accurately identifies which developer is responsible for each error and automatically generates comprehensive reports for managers and focused reports for specific developers. Trend graphs help teams monitor how test results and code quality change over time. Goal features help teams monitor progress toward their quality goals (for instance, "No more than n coding standard violations by [date]" or "No more than n unit testing problems by [date]"). To facilitate workflow prioritization, Jtest creates a prioritized task list after every test. Moreover, Recommended Tasks functionality allows teams to restrict the number of tasks reported per developer per day; this prevents an overwhelming number of tasks from being reported at once.
To help the team leverage Jtest's findings, Jtest also integrates with the Parasoft Group Reporting System (GRS). Using the GRS dashboard and reports, a team gains unprecedented visibility into the quality, scope, and progress of their complete projects? not only their Java code, but also any related Web service functionality, Web application functionality, database functionality, and so forth.
Tagged:
0