You have most probably not added the proper dependencies. Reference: https://stackoverflow.com/a/61429938 I suggest looking into this response for the steps to do so with a dependency management tool, like Maven: https://stackoverflow.com/a/3167378

What are good strategies to find these kind of gaps with automated tests ... You could do a compare on the JSON string from one system to the other or do a SQL EXCEPT statement on the tables if you have access to those. This will tell you what is in one table but not the other. ... or to avoid them in advance? Software versioning is used to indicate if you are looking at the "old" release or the "new" one. API versioning allows you to explicitly test the "old" one or the "new" one. You should always know which you are testing when you are testing it.

assertEquals will give you more information for example if you compare a and b, it will show which one is bigger. But assertTrue will only show the result, like expected true, found false.

Entry point is always a main method. If you're using command-line to run your tests, you use org.testng.TestNG where there is a main method. If you're running tests from IDE or from Maven, there are their own main methods and at some point their code calls TestNG API to execute the tests (or call main method of TestNG if they run tests in different JVM)

I used VirtualBox to install Window 7 and without updates solved the problem. Thanks all One thing I notice why IE11 not working in the host computer is under "About Internet Explorer" it doesn't shows the IE version but instead the Window 10 version. In the working VM, the IE displays the actual version of IE: I believe this is why it is stuck in the webdriver, something to do with the IE itself.

Most probably you recorded something which acts like a session identifier and it's hard-coded when it's supposed to be dynamic like when you're logging in you're getting a dynamic parameter which identifies the session. So you need to perform the correlation of this session identifier. The easiest way of detecting the dynamic parameters is recording the same user action again and compare the resulting JMeter test plans, all values which have changed need to be correlated - extracted from the previous response using suitable JMeter Post-Processors and stored into JMeter Variables Once you replace hard-coded dynamic parameters with the respective JMeter Variables you test should start working as expected. More information: How to Handle Correlation in JMeter

We do not have direct access to the system that is causing the long waits In the environments that you run your automated checks, you can stub out this system (e.g., using MockServer or WireMock), so its response will be under your control. You can then check the integration between your system and the external one with Pact.

Chrome extensions are HTML/CSS/JS based applications. You can test them with Selenium, the steps look something like this: Build the extension to yourdir Start browser and load extension with the argument load-extension= Open url chrome://extensions/ Find the ID of extension under test Open url chrome-extension://ID/options.html to test/configure the option screen Open url chrome-extension://ID/popup.html to test/configure the popup when you click on the icon in the extension bar top right Now use the browser with Selenium and verify the extensions behaviour My personal open source chrome extension Stoppable has some example tests in JavaScript, they configure the options, use the popup and do something on a website to verify the extension is working. I must say I havent released and run the test for years. The Chrome internal pages and locations tend to change. So you might need to adapt it to the latest version of Chrome. A process I had to go through a couple of times already.

In a Jenkins pipeline you can run stages parallel: pipeline { agent none stages { stage('Run Tests') { parallel { stage('Test On agentA') { agent { label "agentA" } steps { sh "run-testsA.sh" } post { always { junit "**/TEST-*.xml" } } } stage('Test On agentB') { agent { label "agentB" } steps { sh "run-testsB.sh" } post { always { junit "**/TEST-*.xml" } } } } } } } https://www.jenkins.io/blog/2017/09/25/declarative-1/

My bad, I was using find_elements_by_xpath instead of find_element_by_xpath Copy paste error from using another line of code

Try one of the Reporters. Available reporters are: cli, json, junit, progress and emojitrain. Since you are using AWS, check out their guide on this topic. It might not be exactly what you are trying to do but it does show the moving pieces. Automating your API testing with AWS CodeBuild, AWS CodePipeline, and Postman

How did you guys set up your vulnerability regression testing? I have used static analysis tools like HCL AppScan and SonarQube. These run against your source code and can be set up as "checks" in GitHub, Azure DevOps, etc. When and how do you deploy the regression tests? You can use a dynamic scanning tool like SortSite or ZAP. How did you use the regression tests in the Definition of Ready and Done respectively? Results of scans we tied to a "release" (stored in a shared directory) and we scanned periodically through the sprint including the last commit before release. My government contracts required we send the results before they would deploy the code. Have you found a way to use Owasp ZAP appropriately in a regression pipeline as well? ZAP has a CLI. I have only run these manually after automated tests pass and let me know the code is stable enough as the scans as they can take some time. You can run anything via CI/CD and shell commands, so if there is a results parsing plugin for your tooling then you are all set. I know if the results are in JUnit (XML) format than there is likely a plugin. I have done this with JMeter tests results output as JUnit format, which were published in Azure DevOps.

DevTool error is often associated with non compatible version of chrome and chromedriver. make sure your browser , driver and OS are compatible . Download the correct OS for the gtilab OS and browser types and versions

Do we need to use a MAC to actually create the tests for the iOS app or is it possible to write them in windows and then export them to the iOS device to run them? You will need a Mac running Appium [server] and you can connect to it like a Selenium Grid Node (via Desired Capabilities). This Mac could be a Mac mini in your office or hosted on a third party cloud service (see Cloud Providers tab of Appium Desktop for examples).

Is there an automation tool that will compare one webpage ... against another ... and detail where the HTML source is different? You could use something off the shelf like DiffNow.com as suggested in this similar StackOverflow question. Otherwise, using a script is probably the easiest.