Enhance "traditional" test flow support/tooling

未关闭
#8,047 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
文档
描述清晰度
需要澄清
活跃度
停滞
技术栈
java

调研方向

首先在 OpenLiberty 文档中搜索 liberty:dev、-DhotTests 和 Surefire/Failsafe 报告,然后查看现有的、关于对运行中的服务器执行测试的指导。完成的标准是提供一个有文档记录且受支持的工作流,或给出明确的建议;任何基于注解的工具都需要 maintainer 就范围作出决定。

由索引模型根据 Issue 内容生成。

描述

Hi folks!

I am unsure on whether this is a feature request or just an inquiry yet as per my search on the documentation I wasn't able to find what I need.

Context:

OpenLiberty is great and it provides a lot of nice tooling which makes developer life easier (once you get used to it that is) yet at the same time it breaks a lot of the "standards" for traditional maven projects, i.e: running the tests against the live server of the application, to do so it is quite simple, just ./mvnw liberty:dev press enter and voila your test run against a live server of your application you can even do that with a single command by passing the -DhotTests flag.

The "problem" arise when you try to get the test reports (like those of surefire/failsafe) as you would do "traditionally" by running mvn test. That command starts, do its thing and, ends, this is great to add it as a step on your CI/CD pipeline, you just add such a step and when it ends your pipeline knows its time to move to the next step, liberty:dev does not make it as simple, specially since it is unclear when its a good time to stop the application after testing. The way I see it, you would either need to set up a timer or capture the output to find specific strings.

Other frameworks have solved this by creating an annotation that would start the server when the tests are running allowing true integration tests without much hassle, see @HelidonTest and @QuarkusTest, they also provide the benefit of starting the server at a random port, allowing for the same worker to run multiple instances of the project (lets say two MR analysis running in parallel on the same computer) without having the ports conflicting.

I hardly doubt I am the first one facing this issue so recommendations would be nice here, and in case its not maybe document such usage.

主要语言
没有语言数据
星标
14
派生
58
平均合并
1 小时
30 天内合并 PR
25

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

OpenLiberty/docs 的其他 Issue

查看 OpenLiberty/docs 的全部 Issue

相似的 Issue

更多 DevOps Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。