We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
由于新增依赖(如接口中新增数据库查询操作)导致回放失败时,建议回显失败原因以降低失败case排查成本。
背景: 1、由于功能迭代,接口中新增了依赖,比如新增了查询数据库、调用三方接口等代码,在回放时会出现空指针异常,进而导致回放失败; 2、回放失败本身无问题,只是当录制的case量比较大时,排查失败case的成本会比较高。
期望: 建议官方在保持原流程不变的情况下,能够对新增依赖导致的失败进行枚举,并支持在web端可以查看这类失败原因
保持原流程不变的情况下,能够对新增依赖导致的失败进行枚举,并支持在web端可以查看这类失败原因
No response
The text was updated successfully, but these errors were encountered:
#474
Sorry, something went wrong.
期待增加该特性
lucas-myx
No branches or pull requests
Is there an existing issue for this?
Description
由于新增依赖(如接口中新增数据库查询操作)导致回放失败时,建议回显失败原因以降低失败case排查成本。
背景:
1、由于功能迭代,接口中新增了依赖,比如新增了查询数据库、调用三方接口等代码,在回放时会出现空指针异常,进而导致回放失败;
2、回放失败本身无问题,只是当录制的case量比较大时,排查失败case的成本会比较高。
期望:
建议官方在保持原流程不变的情况下,能够对新增依赖导致的失败进行枚举,并支持在web端可以查看这类失败原因
Solution
保持原流程不变的情况下,能够对新增依赖导致的失败进行枚举,并支持在web端可以查看这类失败原因
Related issues
No response
Are you willing to submit a pull request to implement this on your own?
The text was updated successfully, but these errors were encountered: