human: Given a hyperedge-centered hypergraph: <hypergraph>, where the center hyperedge is induced by one source paper and its member nodes are the cited papers.

Details of the hypergraph:
Center hyperedge (induced by source paper "an approach and benchmark to detect behavioral changes of commits in continuous integration"):
  Abstract: When a developer pushes a change to an application's codebase, in the form of a commit, the newly introduced behavior may be incorrect. To prevent such regressions, developers rely on a continuous integration (CI) server to run a test suite on the application, at every commit. However, if the test suite lacks the test cases that specify the behavioral changes introduced by this commit, or the changes introduced by previous commits, the bug goes undetected. #R##N#In this paper, we propose an approach that takes a program, its test suite, and a commit as input, and generates test methods that detect the behavioral changes of the commit, i.e., the behavioral difference between the pre-commit and post-commit versions of the program. In essence, this helps developers evolve the test suite (i.e., the application's specification) at the same time they evolve the application. We call our approach DCI (Detecting behavioral changes in CI). It works by generating variations of the existing test cases through (i) assertion amplification and (ii) a search-based exploration of input spaces. We evaluate our approach on a curated set of 50 commits from 5 open source Java projects. Our study exposes the characteristics of commits in modern open-source software and the ability of our approach to generate test methods that detect behavioral changes.

Includes members:
  Member "automatic test improvement with dspot a study with ten mature open source projects":
    also connected through other hyperedges:
      - Hyperedge HE-1 (induced by source paper "suggestions on test suite improvements with automatic infection and propagation analysis")
  Member "bears an extensible java bug benchmark for automatic program repair studies":
    also connected through other hyperedges:
      - Hyperedge HE-2 (induced by source paper "e apr mapping the effectiveness of automated program repair")
  Member "a comprehensive study of pseudo tested methods":
    also connected through other hyperedges:
      - Hyperedge HE-3 (induced by source paper "suggestions on test suite improvements with automatic infection and propagation analysis")
  Member "shadow symbolic execution with java pathfinder":
    also connected through other hyperedges:
      (none)
  Member "reinforcement learning for automatic test case prioritization and selection in continuous integration":
    also connected through other hyperedges:
      - Hyperedge HE-4 (induced by source paper "enhancing dynamic symbolic execution by automatically learning search heuristics")
  Member "how to design a program repair bot insights from the repairnator project":
    also connected through other hyperedges:
      - Hyperedge HE-5 (induced by source paper "ifixr bug report driven program repair")

Question: Please tell me which class the source paper belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.SE(Software Engineering)