Customize PractiTest to fit your Process and Needs Fast and Easy!
You know that no system will fit your process 100% out-of-the-box, so you should look for one that allows you to easily adapt it to your needs and constraints.
With PractiTest you can easily customize your projects in order to match your methodology and process. Without the need to manipulate multiple configuration files or use any scripting development language to modify the system to match your needs.
Customizable Fields and Forms
Whether you want an additional user list, a date field or a list that with values based on the selection of another list, you can do this easily with PractiTest.
Each entity (Requirement, Test or Issue) can be customized to include an unlimited number of fields with the information you need as part of your process.
Set the position in the form itself, each field can be defined as mandatory or recieve a default value. Make fields Mandatory or assign them Default Values.
Click the PLAY button below or download the video (5.6 MB, 3:06)
Groups and Permissions
In PractiTest each user belongs to one or more Groups.
Groups help you manage your project permissions and protect its data by defining what modules can be accessed by each group and what actions they can perform as part of their work.
PractiTest works based on Hierarchical Groups to help you manage your users in a more convenient way.
Organize your information using Private and Public Views
Private and Public views are the most convenient way to organize the work of your team, focusing them on the relevant Information needed to perform their work.
Views let you define the specific entities you want to display as well as the fields you want to show as part of your editable grids.
Define the Workflow and Transitions of your Issues
Define the Workflow of your issues to match your development process. Customizing the States and the transitions between them, then define what group can perform each transition based on your methodology and permission level.
For example, let everyone report a bug, but only a Team Leader assigned it to a developer for fixing.