简体   繁体   English

在生产中运行JUnit集成测试的最佳方法

[英]Best way to run JUnit integration tests in production

I am a Java developer, not a QA engineer, so my question may seem trivial to some. 我是一名Java开发人员,而不是QA工程师,所以我的问题对某些人来说似乎微不足道。

How do I run my integration tests post-deployment? 如何在部署后运行集成测试? In normal build and deployment process, all JUnit tests are executed prior to deployment. 在正常的构建和部署过程中,所有JUnit测试都在部署之前执行。 After deployment is done, testing (as I understand) should be done using other (black box) methods. 部署完成后,应该使用其他(黑盒子)方法进行测试(据我所知)。 But what if I want to periodically check my application using my nice suite of integration tests? 但是,如果我想使用我的一套完整的集成测试来定期检查我的应用程序呢?

What would be a proper way to run IT tests against an existing deployment (including production)? 针对现有部署(包括生产)运行IT测试的正确方法是什么?

Many companies have two environments: production and UAT. 许多公司有两种环境:生产和UAT。 The production environment is the live production site. 生产环境是实时生产站点。 UAT has the same build as production but can be used for testing, trying things out, and comparing if production has a problem. UAT具有与生产相同的构建,但可用于测试,尝试和比较生产是否存在问题。

Should you want to run JUnit tests on production (and like cjds i don't understand why you would), then UAT is the place to do it. 如果你想在生产上运行JUnit测试(和cjds一样,我不明白为什么你会这样做),那么UAT就是这样做的地方。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM