Academic and Industrial Software Testing Conferences: Survey and Synergies
---
paper_title: Gap Analysis between Theory and Practice of Software Testing Methodologies in Indian IT Industry

paper_content:

There are broadly two approaches for software testingmanually or automatically. Manual testing uses the knowledge of the tester to target testing of the system that is assumed to be more error-prone. Automated testing can perform a large number of tests in little time. Software testing is taught to the computer/IT graduates in Indian universities. Tools for manual and automatic testing are available in the market to enhance the productivity and reliability of the testing process. The survey focused on three major aspects of software testing, namely software testing education/ training, testing methodologies/ techniques, and automated testing tools. Based on the survey results, current practices in software testing are reported, as well as some observations and recommendations for the future of software testing in India for academia and industry.
---
paper_title: How healthy are software engineering conferences

paper_content:

Abstract In this article we study the health of software engineering conferences by means of a suite of metrics created for this purpose. The metrics measure stability of the community, openness to new authors, introversion, representativeness of the PC with respect to the authors' community, availability of PC candidates, and scientific prestige. Using this metrics suite, we assess the health of 11 software engineering conferences over a period of more than 10 years. In general, our findings suggest that software engineering conferences are healthy, but we observe important differences between conferences with a wide scope and those with a more narrow scope. We also find that depending on the chosen health metric, some conferences perform better than others. This knowledge may be used by prospective authors to decide in which conferences to publish, and by conference steering committees or PC chairs to assess their selection process.
---
paper_title: Types of collaborative work in software engineering

paper_content:

Abstract This paper is an account on work distribution analyzed from the collaboration point of view. It presents a new classification of the collaborative work in software engineering project. Four types of collaborative work are defined derived from empirical measurements of activities. Mandatory collaborative works are formal scheduled meetings. Called collaborative work is defined when team members call a meeting to solve a problem, which is most often technical. Ad hoc collaborative work is defined when team members work on the same task at the same time and individual work occurs when a team member works on its own on a task related to the project. Data are extracted from the logbook filled out by four team members working on an industrial project that lasts 19 weeks. The characteristics of each type of collaborative activity are described and a quantitative breakdown of how people spend their time in collaboration within a single project is presented.
---
paper_title: Industry academia collaboration model: The design challenges

paper_content:

The Information Technology industry is growing at a healthy rate with businesses heavily dependent on IT applications for their operations. India has become a global hub for IT services export and has witnessed exponential growth of employment opportunities. While the IT industry has felt a pressing need for acquiring and retaining competent talent, academia on the other side has also felt a strong need in terms of producing the necessary quality talent. Hence, a need for industry-academia partnership has been strongly felt to enhance the employability of engineering graduate workforce and make them industry ready. This article discusses the critical design challenges significant for any industry-academia collaboration model in the higher education space [4]. Here, we discuss the design options for such a model, its evaluation strategy and performance parameters, and how it addresses the primary challenges faced by both the stakeholders i.e. industry and academia, in a measurable, scalable and sustainable manner.
---
paper_title: The (Im)maturity level of software testing

paper_content:

A large gap exists between the state-of-the-art in software testing literature, and the state of software testing practice. Empirical research should (and could) play a first class role for bridging this gap. Empirical studies in software testing have focused mainly on the evaluation of techniques for test case selection. But effective selection of test cases by itself is not sufficient to warrant successful testing: we need also empirical studies to start collecting proven patterns that test practitioners can use to predictably solve software testing problems.
---
paper_title: Action research as a model for industry-academia collaboration in the software engineering context

paper_content:

Background: Action research is a well-established research methodology. It is following a post-positivist research philosophy grounded in critical thinking. The methodology is driven by practical problems, emphasis participatory research, and develops practically useful solutions in an iterative manner. Objective: Two objectives are to be achieved: (1) Understanding the state of the art with respect to action research usage in the software engineering literature, and (2) reflecting and providing recommendations of how to foster industry-academia collaboration through action research. Method:} Based on our experience with two action research studies in close collaboration with Ericsson lessons learned and guidelines are presented. Results: In both cases presented action research led to multiple refinements in the interventions implemented. Furthermore, the close collaboration and co-production with the industry was essential to identify and describe the required refinements to provide an in-depth understanding. In comparison with previous studies, we required multiple iterations while previous software engineering studies reported mostly one iteration, or were not explicit regarding the number of iterations studied. Conclusion: We conclude that action research is a powerful tool for industry-academia collaboration. The success of the method highly depends on the researchers and practitioners working in a team. Future studies need to improve the reporting with respect to describing the type of action research used, the iterations, the model of collaboration, and the rationales for changes in each iteration.
---
paper_title: Software testing and industry needs

paper_content:

We've invited five renowned experts in software testing to give a brief answer to an admittedly broad question: does the practice of software testing effectively meet industry needs?
---

Title: Academic and Industrial Software Testing Conferences: Survey and Synergies

Section 1: INTRODUCTION
Description 1: Provide an overview of the challenges and importance of collaboration between academic and industrial software testing communities, and introduce the motivation behind the paper.

Section 2: Objectives
Description 2: Summarize the main objectives of the study, including identifying, analyzing, classifying, and comparing academic and industrial software testing conferences.

Section 3: Research Method
Description 3: Describe the methodology used for identifying and analyzing the conferences, including the selection criteria and data sources.

Section 4: ACADEMIC CONFERENCES
Description 4: List the academic software testing conferences, provide their general properties, and discuss any observed synergies with industrial aspects.

Section 5: INDUSTRIAL CONFERENCES
Description 5: Present the list of industrial software testing conferences, detail their general properties, and analyze any synergies with academic aspects.

Section 6: Summary and possibilities for improvement
Description 6: Summarize the key findings regarding synergies between academic and industrial conferences, identify deficiencies, and suggest potential improvements.

Section 7: CONCLUSIONS
Description 7: Conclude the paper by outlining the overall insights, the remaining gaps, and potential future work.