human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "how do developers test android applications"
  Abstract: Enabling fully automated testing of mobile applications has recently become an important topic of study for both researchers and practitioners. A plethora of tools and approaches have been proposed to aid mobile developers both by augmenting manual testing practices and by automating various parts of the testing process. However, current approaches for automated testing fall short in convincing developers about their benefits, leading to a majority of mobile testing being performed manually. With the goal of helping researchers and practitioners - who design approaches supporting mobile testing - to understand developer's needs, we analyzed survey responses from 102 open source contributors to Android projects about their practices when performing testing. The survey focused on questions regarding practices and preferences of developers/testers in-the-wild for (i) designing and generating test cases, (ii) automated testing practices, and (iii) perceptions of quality metrics such as code coverage for determining test quality. Analyzing the information gleaned from this survey, we compile a body of knowledge to help guide researchers and professionals toward tailoring new automated testing approaches to the need of a diverse set of open source developers.

Connected through hyperedge HE-1 (induced by source paper "to the attention of mobile software developers guess what test your app"):
  with members:
    - "release practices for mobile apps what do users and developers think"
    - "scripted gui testing of android apps a study on diffusion evolution and fragility"
    - "automated test input generation for android are we there yet"

Connected through hyperedge HE-2 (induced by source paper "overcoming language dichotomies toward effective program comprehension for mobile app development"):
  with members:
    - "fusion a tool for facilitating and augmenting android bug reporting"
    - "automated reporting of gui design violations for mobile apps"
    - "machine learning based prototyping of graphical user interfaces for mobile apps"
    - "on device bug reporting for android applications"
    - "mining android app usages for generating actionable gui based execution scenarios"
    - "mdroid a mutation testing framework for android"
    - "pix2code generating code from a graphical user interface screenshot"
    - "an app performance optimization advisor for mobile device app marketplaces"

Connected through hyperedge HE-3 (induced by source paper "detecting and summarizing gui changes in evolving mobile apps"):
  with members:
    - "automated reporting of gui design violations for mobile apps"
    - "machine learning based prototyping of graphical user interfaces for mobile apps"
    - "crashscope a practical tool for automated testing of android applications"
    - "automatically discovering reporting and reproducing android application crashes"
    - "automated test input generation for android are we there yet"

Connected through hyperedge HE-4 (induced by source paper "mdroid a mutation testing framework for android"):
  with members:
    - "enabling mutation testing for android apps"
    - "a large scale empirical comparison of static and dynamic test case prioritization techniques"
    - "automated test input generation for android are we there yet"

Connected through hyperedge HE-5 (induced by source paper "mobicomonkey context testing of android apps"):
  with members:
    - "on device bug reporting for android applications"
    - "automatically discovering reporting and reproducing android application crashes"

Question: Please tell me which class the center node 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)