Defects4j:run.dev.tests 引用什么?

发布于 2025-01-09 15:38:30 字数 1107 浏览 0 评论 0原文

我试图了解 run.dev.tests 引用的是什么。

当我在 Defects4j 中运行测试命令时,它会编译并运行测试。执行从 Project.pm 调用的 run_tests 子例程。

run_tests 子例程被调用并返回 _ant_call_comp 子例程,该子例程从 Project.pm 调用并且需要至少 2 个参数。

由于目标是参数之一,我认为 run.dev.tests 是 ant 构建文件中的目标,但我在任何地方都找不到它。

在其他(第四和第五个屏幕截图)中,正在传递 _ant_call_comp 子例程compile.tests,它是构建文件中的目标。但我在所有文件和文件夹中都找不到 run.dev.tests 。

有人可以指出正确的方向吗?

run_tests 子例程从 Project Perl 模块调用

子程序代码

_ant_call_comp 子例程

在此处输入图像描述

在此处输入图像描述

I am trying to understand what is run.dev.tests referencing to.

When i run test command in Defects4j it compiles and run tests. run_tests subroutine which is called from Project.pm is executed.

run_tests subroutine is called and returns _ant_call_comp subroutine which is called from Project.pm and requires at-least 2 arguments.

since a target is one of the parameter I think run.dev.tests is a target in ant build file but i can't find it anywhere.

In other (4th and 5th screenshot) _ant_call_comp subroutine compile.tests is being passed that is a target in build file. But I can't find run.dev.tests anywhere in all files and folders.

Can someone please point be to the right direction?

run_tests Subroutine being called from Project Perl Module

Subroutine code

_ant_call_comp subroutine

enter image description here

enter image description here

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

想挽留 2025-01-16 15:38:30

run.dev.tests (或者通常是 _ant_call 中的目标参数)子例程引用 Defects4J 的顶级构建文件

Defects4J 的顶级构建文件定义了允许用户或客户端程序以编程方式编译和测试其任何工件的所有目标。为了解决项目和/或工件特定的差异,Defects4J 使用三个构建文件的层次结构:

  1. 顶级构建文件(即所有工件的统一接口)。
  2. 特定于项目的构建文件(例如 Lang .build.xml)。
  3. (原始)工件构建文件(即签出项目版本的构建文件)。

run.dev.tests (or generally the target parameter in the _ant_call) subroutine is referring to a target in Defects4J's top-level build file.

Defects4J's top-level build file defines all targets that allow a user or client program to programmatically compile and test any of its artifacts. To account for project and/or artifact-specific differences, Defects4J uses a hierarchy of three build files:

  1. The top-level build file (i.e., the unifying interface to all artifacts).
  2. A project-specific build file (e.g., Lang.build.xml).
  3. The (original) artifact build file (i.e., the build file of a checked-out project version).
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文