Skip Navigation LinksHome Page > Forums > Rapise Forums > Rapise Issues & Questions > Running tests on remote m...
I am looking for test automation solution to automate test cases based on Microsoft Dynamics AX2012. I would like to do a POC to evaluate Rapise against my project needs. Before i start building my POC, i would like to clarify on the below:
1. Does Rapise support test automation of Microsoft Dynamics AX2012
2. Can Rapise be integrated into CI/CD pipeline.
3. Does Rapise come with an integration package/plugin for integration with Visual Studio
4. Can automated test cases of Microsoft Dynamics AX2012 be run on remote desktops and remote VMs?
5.If the test cases can be run in remote desktops and VMs, do they need a live session until the test cases complete running? i.e, if i trigger the test from my local desktop, do the physical machine from where i trigger the tests and the remote desktop/VM where the tests are running needs to be logged in all the time while tests are running or the tests can run even if the local machine and remote machine/VM are in locked state?
I would recommend contacting firstname.lastname@example.org to get more specific answers to your questions, and we can arrange a live demo, but in general:
You can use a self-host agent to run your pipeline. Since Azure agents cannot communicate with your local DB, you can set up a self-hosted agent on your local machine. Your local is accessible to the self-hosted agent.
In order to run Integration Tests in your release pipeline. You can include your Test projects or test assembly dll files in the artifacts published in your build pipeline. So that your Integration test projects are accessible to the test tasks in your release pipeline.
Include your test files in the artifacts. You can add a second publish build artifacts task in your Build Pipeline. Specify the Path to publish to the location of your test files. All these problems related to remote machine and integration is discussed in the AWS online training.
Run tests in the release pipeline by adding the VsTest task or other test tasks in your release pipeline. The release pipeline will download your artifacts to folder $(System.DefaultWorkingDirectory).
Visual Studio Test task and Dot NetCore CLI task automatically publish test results to the pipeline, while tasks such as Ant, Maven, Gulp, Grunt, .NET Core, and Xcode provide publishing results as an option within the task. Besides you can use Publish Test Results task.
Here are some articles you can refer to:
Running tests on a remote machine is a common practice in software development. This allows for testing on different configurations, environments, and platforms. The tests can be run on a dedicated test machine or on a virtual machine in a cloud environment.
Integration with DevOps is important for automating the testing process and incorporating it into the development workflow. This can be done through the use of continuous integration and continuous delivery (CI/CD) tools, such as Jenkins, Travis CI, or CircleCI. These tools can automatically run tests on a remote machine whenever changes are made to the codebase, and can also be configured to deploy the code to production if all tests pass.
Another way to integrate tests with DevOps is by using test automation frameworks like Selenium, Appium, or TestComplete. These frameworks can be integrated into the CI/CD pipeline and can run tests on remote machines and report the results back to the development team.
Overall, running tests on a remote machine and integrating them with DevOps allows for more efficient and effective testing and helps ensure that the code is of high quality and ready for deployment.
And if you have any questions, please email or call us at +1 (202) 558-6885