alibaba / intelligent-test-platform

intelligent-test-platform

概述

Markov是在测试转型大背景下自研的新一代功能测试平台，相较于传统的功能测试框架具有着诸多的优点，比如可视化用例编写管理、分布式的沙盒环境和测试数据构建、测试流程pipeline管理。此外，基于该平台还衍生出了许多智能化测试技术，如基于朴素贝叶斯的用例推荐、参数组合膨胀过滤的用例推荐、基于用例编排算法的智能回归技术、基于用例画像的智能排查系统、精准智能测试等。我们可将Markov视为新一代的功能测试框架，相对于传统经典的测试框架(如pytest)+jenkins的模式，Markov模式对于使用者的门槛更低，能让不懂测试的开发和算法同学简单的进行自助测试，达到了让天下没有难做的"测试"的目标。

主要功能

1.pipeline管理

• pipeline即一份配置文件，与功能测试而言主要的两部分，第一个是测试环境部署相关的，主要是各种参数(比如ip，部署脚本，docker等参数)，第二个是case执行相关的参数（包括了该模块的该如何发送，校验，页面上该展示何种数据源等）。可以抽象理解成，pipeline仅为部署页和用例调试页设定了特定模块所需配置参数。此外，pipeline设计为通用的扩展形式，比如用户可自定义对比测试/压测/集成测试等。

2.用例管理

• 可视化的用例管理中，Markov定义了一种面向功能测试的通用页面结构，包含了用例名/描述/业务分组/标签/测试数据/发送query/期望结果等元素，结合pipeline中的测试流程配置，实现了动态渲染用例编辑页的结果，让测试平台能接入更多的测试模块。

3.测试环境管理

• 可视化的测试环境管理，Markov基于分布式容器部署技术，实现了在测试机上部署多容器能力，支持了镜像/rpm/基线等多种部署方式，让测试资源最大化利用，并支持页面化的环境部署/锁定/删除/异常检测等完善的管理能力。(本期只开放前端可视化，具体测试部署暂为开放)

4.用例编写和执行

• 支持可视化的环境选择/测试数据修改后一键执行，透出实时日志和结果。后端执行引擎结合pipeline流程达到动态化load执行插件，以此调度，十分灵活。

5.回归测试

• 支持页面化选取批量用例和测试环境，可选择多种回归模式(本期开放caseBycase的基本模式)，执行完成后可产出回归测试报告。

快速开始

开发环境:IDEA

1.拉取git代码库

https://github.com/alibaba/intelligent-test-platform

IDE配置端口为8888，java8

2、搭建本地mysql环境

在本地安装mysql后启动（mysql版本要求8.0及以上），设置用户名和密码

3、创建数据表

source database.sql

4、修改项目的mysql配置

修改项目文件src/main/resources/application.properties，改为步骤2中设置的mysql用户名及密码

5.配置pipeline流程配置

启动服务后，点击 配置-pipeline，在pipeline编辑框中输入并保存demo中的pipeline内容(pipeline_demo)

6.Demo试用吧！

DEMO演示

1.pipeline管理DEMO

2.用例管理DEMO

3.测试环境管理DEMO

• 测试环境管理页

• •测试环境部署页

4.用例执行DEMO

5.回归测试DEMO

• 回归测试任务编辑

• 回归任务进度

• 测试报告详情页

6、体验智能化feature

点击查看Intelligent.md

2期开源计划

我们将按照计划进行开源，当然如果你有更感兴趣的方向，我们可以调整开源的优先级.

Markov Framework 未发布功能：

1.测试数据源管理。

2.分布式调度

3.智能排查。

4.用例分支管理。

5.基于容器化的测试环境部署

6.UT

7.功能AB-Test

8.用例画像系统

9.markov认证系统

10.定时调度系统

11.多bu权限管理系统

等..

联系我们

Markov由阿里集团-新零售智能引擎事业群-广告产品技术事业部-技术质量-引擎&基础测试及平台团队荣誉出品，[email protected]和github issue联系和反馈。

钉钉沟通群：

License

intelligent-test-platform's Issues

使用flyway管理数据库版本

错误信息：
Invocation of init method failed; nested exception is org.flywaydb.core.api.FlywayException: Found non-empty schema(s) markov_demo but no schema history table. Use baseline() or set baselineOnMigrate to true to initialize the schema history table.

修改意见：

application.properties

spring.flyway.default-schema=markov_demo
spring.flyway.locations=classpath:db/migration

修改为

spring.flyway.default-schema=markov_demo
spring.flyway.locations=classpath:db/migration
spring.flyway.baseline-on-migrate=true

空指针异常

打开智能用例推荐，智能用例生成报java.lang.NullPointerException

支持netty框架protobuf协议请求游戏接口需求

后端java能不能实现使用netty框架发送protobuf协议到游戏接口的实现

angularjs1.6太老旧了，建议前端改成用react+ant design开发，以ant design pro为基础开发

如题
ant design、ant design pro也算是阿里出品，angularjs是淘汰了的技术了。

顶顶群失效了

部署环境菜单中，构建后的环境无法查看详情

看html里面只给详情按钮了个<a>，没绑定任何东西。

使用idea2020.1 编译失败，Error:(3, 19) java: 程序包net.sf.json不存在

网页访问失败是什么原因？

用eclipseIDE启动软件，访问http://xxxxxx:8888或http://xxxxx:8888/index.html
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.

java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:418) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:260) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1594) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_191]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_191]

2020-05-15 12:30:38.128 INFO 20812 --- [nio-8888-exec-2] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.

java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:418) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:260) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1594) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_191]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_191]

2020-05-15 12:30:38.128 INFO 20812 --- [nio-8888-exec-3] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.

java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:418) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:260) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1594) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_191]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_191]

2020-05-15 12:30:38.128 INFO 20812 --- [nio-8888-exec-5] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.

java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:418) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:260) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1594) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_191]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_191]

2020-05-15 12:30:38.128 INFO 20812 --- [nio-8888-exec-1] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.

java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:418) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:260) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1594) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_191]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_191]

2020-05-15 12:30:38.160 INFO 20812 --- [io-8888-exec-11] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.

java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:418) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:260) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1594) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_191]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_191]

2020-05-15 12:30:38.128 INFO 20812 --- [nio-8888-exec-4] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.

java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:418) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:260) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1594) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_191]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_191]

2020-05-15 12:30:38.161 INFO 20812 --- [nio-8888-exec-3] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.

java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:418) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:260) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1594) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_191]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_191]

2020-05-15 12:30:38.162 INFO 20812 --- [nio-8888-exec-8] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.

java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:418) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:260) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1594) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_191]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_191]

2020-05-15 12:30:38.161 INFO 20812 --- [nio-8888-exec-9] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.

java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:418) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:260) ~[tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1594) [tomcat-embed-core-9.0.33.jar:9.0.33]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_191]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.33.jar:9.0.33]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_191]

遗传算法适应度函数

这个适应度函数 F(x) = ∑(k+u*Gxi/Wxi) ，麻烦问一下，这个分母 Gxi和 分子Wxi具体含义是什么? 谢谢！

请问，平台还在维护嘛？后续开源计划是什么样的？

请问，平台还在维护嘛？后续开源计划是什么样的？

项目前端启动问题

老师，您好，这个工程的前端框架麻烦帮忙解答一下如何启动？
我在resource中的static中找到的应该就是前端部分，但是这个具体应该如何调试启动能？具体命令烦劳指点一下，谢谢！
还有，启动后，对应前端的系统具体网址应该如何进入，看视频中网址是 http://localhost:8881/，是这个吗？

智能生成用例功能异常

startAICaseGenerator()的入参取的是textarea中的defaultGeneConf，但是实际上修改textarea的值，不改变请求的入参？

智能用例生成，这部分在覆盖的过程中能达到94%，但无法完全覆盖，这个在实际的场景中，不能达到100%的覆盖必然存在遗漏，请问这个功能实际的意义是什么呢？

老师，您好，智能用例生成，按github的说明，这个最高是94%的覆盖，无法达到全量覆盖，但是，如果真实的环境中，无法达到100%的覆盖必然存在覆盖遗漏，即会存在6%的风险，那这个智能用例生成的实际意义是什么呢？无法全量覆盖，使用的话，为了安全是不是用枚举+人工筛选效果 > 智能推荐，毕竟这个推荐部分不可控啊！

"pipeline编辑"粘贴内容后，保存提示“null”.

您好，我对您项目的智能化技术很惊喜，想使用一下。
但我是个编程小白，JAVA从没用过，这两天按照您给的教程，磕磕碰碰的到了最后一步（其实不确定前面的步骤是不是正确）。
我在"pipeline编辑"里复制粘贴了“pipeline_demo”内的内容，然后试图保存，结果网页提示“null”，请问这是什么原因呢？
是因为“数据源编辑”没有输入内容吗？ 如果是的话，应该输入什么呢？
期待您的回复，祝好！

可不可以提供一下关于pipeline中数据源配置的说明？

Unknown collation: 'utf8mb4_0900_ai_ci'

初始化数据时候报这个错误，是需要使用mysql8吗 ？ 目前我是用的数据库是docker mysql:5.7

钉钉群二维码已失效

更新 JSON 处理包以及管理项目依赖

建议使用 https://github.com/json-path/JsonPath 以及 Jackson 来处理 JSON 和 JsonPath。
目前发布的项目中，粗略看 Toolkit 和 JsonPathParser 并没有实际的代码使用，如果未使用是否可以先减少对老旧第三方包的依赖，降低使用者的部署门槛。

部署环境中，多环境的展示有误

在pipeline的hostList里面添加多个host，然后跳转到部署环境页面，host列表中只展示hostList中最后一个Host。
考虑是EnvsProcessor类下面的findByScenarioId方法里面，在遍历hostList的时候，由于envUnit在循环体外创建，所以循环体内部使用的是同一个envUnit对象，所以最后return这个list的时候，里面只有一个envUnit，只不过属性的值被更新了而已。
建议这里优化一下。

参数膨胀问题

当json数据有多层次，并且上下层关系同名时，会出现匹配不到的问题。需要修改匹配逻辑

/**
     * param 格式为a.b.c:xxx
     * map 可以去掉，获取每次的map集合
     * appendMap 获取最终的map集合
     *
     * @param param
     */
    private void dot2Json(String param, Map map, Map appendMap) {
        if (null == map) {
            map = new HashMap<>();
        }
        String[] o = param.split(":");
        String[] split = o[0].split("\\.");
        // 值为空时，默认为空字符串
        String content = o.length >= 2 ? o[1] : StrUtil.EMPTY;
        Map<String, Object> resultMap = new HashMap<>();
        Map<String, Object> deepMap = appendMap;
        int deep = -1;
        for (int i = 0; i < split.length; i++) {
            if (i == split.length - 1) {
                resultMap.put(split[i], content);
            } else {
                Object obj = deepMap.get(split[i]);
                if (obj != null) {
                    if (obj instanceof Map) {
                        deepMap = (HashMap) obj;
                        deep = i;
                    }
                }
                resultMap.put(split[i], new HashMap<>());
            }
        }
        if (split.length > 1) {
            for (int i = split.length - 2; i >= 0; i--) {
// **这里会有问题**
                Map<String, Object> tempMap = (HashMap) resultMap.get(split[i]);
                tempMap.put(split[i + 1], resultMap.get(split[i + 1]));
                if (i == deep) {
                    deepMap.put(split[i + 1], resultMap.get(split[i + 1]));
                }
            }
            map.put(split[0], resultMap.get(split[0]));
            if (-1 == deep) {
                deepMap.put(split[0], resultMap.get(split[0]));
            }
        } else {
            map = resultMap;
        }
    }

无法clone代码

“http://gitlab.alibaba-inc.com/engine-test-platform/markov_open”连接访问失败，无法clone代码，这个是公司内网的地址？

这个是不是不适合做http/https这样这种接口的测试呢？这个主要适用于什么样的测试呢？

这个是不是不适合做http/https这样这种接口的测试呢？这个主要适用于什么样的测试呢？
我看代码底层是执行插件之类的，就是页面上配置管理的pipeline的内容，然后用逐个调 IPlugin p来调用插件，这个只是个接口欸，没有具体实现方法呀？没有看到最终怎么实现的，可能是我没看到，请求解答一下哈~谢谢。
还有一个是页面上发送请求的数据出入底层，我没有看明白出入之后到底是用来干啥的，这个请求看样例格式类似http请求的json格式。

能否支持从 testlink 导入测试用例

如题，对于一些在 testlink 中积累了大量测试用例的公司来说，如果有这样的一个功能，对于快速引入 markov 有极大的帮助。

生成智能用例报错

给的数据库里面没有got_case_generate_task这张表
org.springframework.jdbc.BadSqlGrammarException:

Error updating database. Cause: java.sql.SQLSyntaxErrorException: Table 'markov_demo.got_case_generate_task' doesn't exist

Docker 镜像提供方便快速部署

项目启动报错 Error creating bean with name 'flywayInitializer' defined in class path resource

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Invocation of init method failed; nested exception is org.flywaydb.core.api.FlywayException: Found non-empty schema(s) markov_demo but no schema history table. Use baseline() or set baselineOnMigrate to true to initialize the schema history table.
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1796) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:595) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:321) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:310) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:882) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:878) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:550) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
at com.alibaba.markovdemo.MarkovDemoApplication.main(MarkovDemoApplication.java:12) [classes/:na]
Caused by: org.flywaydb.core.api.FlywayException: Found non-empty schema(s) markov_demo but no schema history table. Use baseline() or set baselineOnMigrate to true to initialize the schema history table.
at org.flywaydb.core.Flyway$1.execute(Flyway.java:187) ~[flyway-core-6.4.2.jar:na]
at org.flywaydb.core.Flyway$1.execute(Flyway.java:159) ~[flyway-core-6.4.2.jar:na]
at org.flywaydb.core.Flyway.execute(Flyway.java:530) ~[flyway-core-6.4.2.jar:na]
at org.flywaydb.core.Flyway.migrate(Flyway.java:159) ~[flyway-core-6.4.2.jar:na]
at org.springframework.boot.autoconfigure.flyway.FlywayMigrationInitializer.afterPropertiesSet(FlywayMigrationInitializer.java:65) ~[spring-boot-autoconfigure-2.2.6.RELEASE.jar:2.2.6.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1855) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1792) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
... 18 common frames omitted

请问这个问题如何解决

智能用例生成适用范围是什么

智能用例生成适用于将各种函数串起来的业务类的用例吗？还是只是用来生成接口用例呢？

pom <classifier>jdk15</classifier>

	<dependency>
		<groupId>net.sf.json-lib</groupId>
		<artifactId>json-lib</artifactId>
		<version>2.4</version>
		<classifier>jdk15</classifier>
	</dependency>