[Feature] 在测试环境录制,又在测试环境回放,当动态类,中间件,数据库,外部调用等mock数据不存在时,能走真实调用.

Open
#474 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
testing-qa

Research direction

The issue describes fallback behavior for missing mocks during replay across dynamic classes, middleware, databases, and external calls, but names no files, tests, or entry points. Start by locating the replay handling for missing mock data and determine how real calls are currently blocked. Done means the fallback behavior is defined and covered across the listed call types.

Written by the indexing model from the issue text.

Description

enhancement :star: good first issue :+1:
Is there an existing issue for this?
  • I had searched in the issues and found no similar issues.
Description

在测试环境录制,又在测试环境回放,当动态类,中间件,数据库,外部调用等mock数据不存在时,能走真实调用.
背景:

  1. 测试环境机器1,部署同线上环境一样的代码,作为稳定机器环境提供给上下游系统使用。
  2. 测试环境机器2,部署研发迭代版本进行新需求开发。

使用方式:

  1. 在机器1上录制。
  2. 在机器2上回放。

期望:
因为中间件,数据库环境都一样,只是代码分支不一样,所以希望回放时当mock数据没有时,能走真实调用,这样更容易利用稳定版本的流量数据来回归不稳定版本中的问题....

Solution

在测试环境录制,又在测试环境回放,当动态类,中间件,数据库,外部调用等mock数据不存在时,能走真实调用.

Related issues

No response

Are you willing to submit a pull request to implement this on your own?
  • Yes I am willing to submit a pull request on my own!
Dominant language
Java
Stars
566
Forks
141
Avg merge
36m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from arextest/arex-agent-java

All issues in arextest/arex-agent-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.