Best Practices for New Test Targets¶
Here are a list of best practices to follow when creating new test targets.
Align your targets with your portfolio. : Consider your application portfolio and make sure that the targets you create are well-aligned with your portfolio.
For Web targets, if multiple applications share a single hostname, create a separate target for each application. Each application should have its own target.
: For multiple applications that share a common hostname (such as http://mycompany.com), it is possible, though not best practice, to use a single Web target to test multiple applications.
Instead, we recommend that you create a separate target for each component application. This improves the value and insights that you can gain from the vulnerability statistics displayed on the **DASHBOARD** panel. It alsp helps to ensure that each component application receives appropriate test coverage.
Provide a friendly display name for targets. : When you create a target, the name you enter becomes the display name for that target throughout the Managed Services Platform interface. It is possible to give one target the same name as another, but this may cause issues later on. We recommend that you use a unique user-friendly name instead.
**Note:** When you hover the mouse over a target’s name, the Managed Services Platform can display an additional identifier. For example, it can display the URL associated with a Web target.
For Web targets, verify URLs before you schedule tests. : Once you create a target, you cannot edit the target URL field. To change the URL, you must delete the target and re-create it. Therefore, verify that the URLs are correct for your Web targets before you create them. Note that each Web target must have a unique URL.
Parent topic:Creating Schedules for Test Targets
Related information