Tag Info

New answers tagged

0

Even I am facing the same type of error: Deploying New 'GitMavenWASSample-0.0.1-SNAPSHOT' to IBM WebSphere Application Server Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Failed to install artifact: at ...


0

If the tests are automated, run them as early and as often as possible on the main branch. In the best case, you can pinpoint which merge had the culprit. At the very least, it will narrow the list of suspects. That's assuming the tests don't cost you anything -- no manual steps, no extra servers and licenses beyond those you have anyway.


1

I asked a similar question awhile back. Perhaps the answers located here may also be of assistance as you evaluate what would be the best fit for your organization. Based on the feedback I received from stackexchange, I modified our process to a mini-regression suite at every release. It tests only the showstopper level features. If I don't find bugs, I can ...


2

When it comes time to complete a roll out we do the following. Its important to note this phase is ran on a previous version test template with no previous data. We are also in the process of pulling a portion of our regression suite to automation. Shallow exploratory. Test basic navigation and control functionality per page. Deep Exploratory. Similar to ...


2

Apologies in advance for a quick/simplistic answer - it's crunch time here! My current client have automated around 80% of regression testing, the rest is done manually with an offshore team, where the basic rule of thumb is: "If you change B, test A and C" i.e., everything around the change - there's no point in your regression team (or the automated ...



Top 50 recent answers are included