- Last Active
- Members, Admin, Staff
One of the recommendations is to check-in your assets as a Project folder (not the workspace) that contains all of the artifacts (.pva, .pvadd, .pmpdd, etc) that are associated with the service you virtualized.
I recommend checking out the webinar presented by @Chris Colosimo that goes over some of the best practices to automate the deployment of these artifacts for continuous testing. The webinar can be found here . I have summarized the video for your convenience.
11:40 --> Review of artifacts and their purpose(.pva, .pvadd, .pmpdd, .pjcdd)
14:30 --> Demonstration of artifacts in workspace
20:08 --> Source Control Workflow
27:50 --> Deploying from Source Control & automation workflow
(introduction to Continuous Testing Platform)
This is Omar by the way5
Resolving Community License Error
When activating your Community License for the first time, you may run into the following:
Community License is not currently available. Please try again later and contact Parasoft if you are still unable to access Community License.
This error can occur when the license connection is blocked by a firewall or there is a corporate proxy in place.
1) Check for updates. It is likely that any licensing issues have already been resolved with the latest updates made to Community Edition.
2) Ping “www1.parasoft.com”. An unsuccessful ping test indicates that there may be a firewall blocking this connection. If so, you should consult with your IT department to allow network access for your Community Edition.
3) Check your IE browser settings to verify if your machine is using a Proxy:
- Open IE
- Click the Tools button
- Click on Internet Options
- Click on the Connections Tab
- Click on LAN settings
If so, try adding these same settings within your CE instance in Parasoft>Preferences>Proxy.
Enable “Automatic Configuration script” or “Proxy Settings” depending on your current configurations.
After applying the appropriate settings, click Okay. Reopen your Parasoft Preferences and re-apply your License.
If the behavior persists, disable the initial proxy setting, “Automatic Configuration script”, and enable the secondary option, “Same Proxy Server for all Protocols”.
After applying the appropriate settings, click Okay. Reopen your Parasoft Preferences and re-apply your license.
If none of these steps resolve your license error or you continue to experience any unexpected behavior, please don’t hesitate to contact our Support team at firstname.lastname@example.org so that we may assist you with resolving this.9