Scam2007 jiang

The document discusses whether the Groovy programming language is better than Java for testing. It outlines some of the pros and cons of each approach. While Java and JUnit tests are performant and well-supported, Groovy and the Spock testing framework make tests more readable, easier to write, and help describe expected system behavior through features like mocking and hamcrest matchers. Migrating existing Java tests to Groovy would require learning a new language but allow exploring its testing advantages without impacting production code. In conclusion, both have tradeoffs and the best approach depends on the specific project needs and developer preferences.

Steve Jones - Team-based Version Control

Red Gate Software

This document discusses best practices for team-based database development using version control. It emphasizes that all database code and configuration should be stored in version control for collaboration and risk reduction. The document recommends standards for naming conventions, coding styles, and development processes. It also demonstrates how to configure tools to support automation and efficient workflow within development teams. Effective communication, coordination, and adherence to source control principles are key to smooth team collaboration on database projects.

The document discusses best practices for writing tests, including that tests should prove designed behaviors, focus on testing single units of code or closely collaborating classes, and be readable with short, clearly named methods that clearly indicate what is being tested and the expected result. Tests should follow guidelines like having a single concept, being short and readable, testing behaviors rather than configurations, using a build-operate-check structure, and having one assertion per test.

Code Review Matters and Manners

A code review is basically a technical discussion which should lead to improvements in the code and/or sharing knowledge in a team. As with any conversation, it should have substance and form. What’s involved in a good code review? What kind of problems do we want to spot and address? Trisha Gee will talk about things a reviewer may consider when looking at changes: what potential issues to look for; why certain patterns may be harmful; and, of course, what NOT to look at. But when it comes to commenting on someone’s work, it may be hard to find the right words to convey a useful message without offending the authors - after all, this is something that they worked hard on. Maria Khalusova will share some observations, thoughts and practical tricks on how to give and receive feedback without turning a code review into a battlefield.

Waterfalls for agile cambridge

The document discusses various "mini-waterfalls" that can emerge in Scrum teams through defined roles like analysts, developers, and testers working sequentially rather than collaboratively. Some examples provided include analysts completing work before passing it to developers or testing only occurring at the end after development is finished. This siloed work can reduce understanding, flexibility, speed, and quality. The document suggests empowering cross-functional teams and automating work to avoid these anti-patterns. It prompts readers to examine their own teams for similar issues and ways to continuously improve.

Waterfalls for Agile in a bag

The document discusses issues that can arise from siloed roles in Scrum teams, such as developers, testers, and Scrum Masters acting as separate functions. This leads to reduced understanding between roles, bottlenecks when resources are unavailable, and an overall lack of team accountability. The document suggests that defining roles rigidly can cement separations and inhibit collaboration, flexibility, and process improvement. It argues teams should avoid "mini-waterfalls" between roles and instead strive for full cross-functionality, shared understanding of requirements, collective responsibility, and empowerment of self-organizing teams.

АННА ТИМОФІЄВА & СЕРГІЙ МАЛИНОВСЬКИЙ «Tools and Tips of video connection test...

QADay

Presentation delex

Alexander Pushkarev

1) The document discusses test automation challenges at WorkFusion including long test run times, low coverage, and technical debt. 2) It proposes adopting a "feature test" approach between unit and UI tests to help address these issues by mapping manual test cases to automated scenarios. 3) Key steps would be to identify redundant tests, delete obsolete code, start a unit/integration test initiative, and get additional resources to help scale the efforts. Outcomes and lessons learned would be reviewed.

TDD - Christchurch APN May 2012

Alan Christensen

Babysitting your orm essenmacher, adam

Adam Essenmacher

This document summarizes a presentation about babysitting your ORM with a custom TFS build. The presentation discusses integrating ORM performance analysis into your ALM process using TFS and a profiling tool. It reviews ORMs and CI/TFS, demonstrates why measuring an ORM's behavior is important using examples, and shows a demo of writing tests, committing code through a gated check-in, and viewing profiling results on individual tests to detect issues like N+1 queries. The goal is to apply simple ideas and best practices to gain real, measurable ROI from monitoring ORM performance in your builds and tests.

Increase selenium tests stability via java script

The document discusses using JavaScript instead of WebDriver to increase the stability of Selenium tests. UI tests are unstable due to complex, asynchronous modern user interfaces. Many interfaces are based on pre-made components that may not be thoroughly tested individually. These components often have internal APIs that are more reliable than WebDriver for interacting with them. The document provides examples of using JavaScript to synchronize tests and work around issues like multiple frames and custom controls. It emphasizes using JavaScript as a temporary workaround and understanding why standard WebDriver approaches do not work in certain cases.

How to get the most out of code reviews

JavaDayUA

As developers we always look for ways to do things faster, better, and automate as much as possible. We write code in top-notch IDEs that have static code analysis, automatic refactoring and so on, we run unit tests, we use CI servers, and issue trackers, we adopt agile practices to get feedback and deliver as fast as possible. As far as code review practice goes, there’s still a lot to be improved, and in this talk I’m going to tell you how you can perform efficient, transparent and useful code reviews.

RoboCon 2018: How did we get here? Where do we go next?

Pekka Klärck

This document summarizes the history and development of Robot Framework, an open source test automation framework. It discusses how Robot Framework originated from the creator's master's thesis prototypes in 2004-2005. It was later developed at Nokia Networks in 2005 and open sourced in 2008. It is now widely used globally and in Finland. The document outlines current and future plans for new releases and libraries to expand Robot Framework's capabilities and growing user base.

Model Driven Developing & Model Based Checking: Applying Together

Iosif Itkin

The document discusses how model driven development (MDD) and model based testing (MBT) can be applied together. It proposes creating a multi-tiered model to describe concurrent, distributed systems at different levels of abstraction. This model can then be used to both guide code development and perform dynamic and static testing of the system. Key aspects include mapping the model to code using classes, collecting runtime traces to check the model, and transforming the model to formal languages like Promela to enable model checking with tools like Spin. The overall goal is to integrate these capabilities into an IDE plugin to help developers design, implement and verify complex systems using models.

UK star ultimate testing survival

Viktor Slavchev

This document provides tips for surviving as a tester based on stories that portray testing as easy but can turn difficult. It summarizes that: 1. Documentation is often lacking, tools are imperfect, and real-life projects introduce challenges beyond what stories suggest. 2. Risk-driven testing is recommended over artifact-driven testing to understand core functionality and risks through techniques like premortems and risk lists. 3. Using oracles like documentation, common sense, and experience can help spot problems, but oracles have more depth than commonly understood. 4. Automation should support testing by being consistent and efficient with short, deterministic scripts rather than replacing testing or focusing on end-to-end UI tests

Type mock isolator

MaslowB

This document discusses unit testing and mock frameworks. It defines common terms like unit test, fake, stub, and mock. It describes the strengths and weaknesses of unit testing. It then introduces TypeMock as a mock framework that can fake static, sealed, or non-public elements without requiring design changes for testability. The document also briefly debates the pros and cons of dictating design for testability and mentions some research on the benefits of test-driven development.

Staying Ahead of the Curve

Why test automation projects are failing

Summarizing the experience of dozens successful and unsuccessful projects, the author of the presentation explains the most common reasons of test automation projects failures. Also the speech will cover some best practices and the ways to make UI test automation beneficial. From the presentation you'll find the answers to the following questions: - Why automated testing is expensive? - What are the reasons of long test executions? - What makes automated tests fail unpredictably? You'll also be able to find solutions to get rid of typical failures on your test automation project.

The Bumpy Road Towards Continuous Delivery

Benjamin Bischoff

This document summarizes Benjamin Bischoff's presentation on the challenges trivago faced in establishing continuous delivery of their hotel search product releases. Initially, trivago relied heavily on manual testing which led to long release cycles and unstable features. They created a centralized automation team to develop test frameworks, pipelines and ownership models. This empowered teams to integrate automated testing earlier. While technical hurdles around infrastructure and frameworks remained, changing mindsets around the value of automation through education and communication was also critical to their progress towards continuous delivery.

Software testing

Inthra onsap

This document discusses different types of software testing techniques. It outlines the typical testing workflow which involves identifying bugs through input/output testing and then fixing issues found in the code, specifications, or underlying libraries/compilers. It also describes various testing strategies like assertions to validate conditions, fault injection to test error handling, unit/integration/system testing, coverage testing to evaluate code execution, and stress testing to evaluate performance under heavy loads or edge cases. The goal is to find and address issues prior to releasing software to production.

Writing Tests Effectively

Paul Boocock

Microsoft Fakes, Unit Testing the (almost) Untestable Code

Unit Tests with Microsoft Fakes

This document discusses unit testing and the Microsoft Fakes framework. It begins with an overview of different types of software tests like unit tests, integration tests, and user acceptance tests. It then discusses why unit tests are important and some conventions for writing unit tests. Dependencies and coupling are mentioned as challenges for unit testing. The document introduces Microsoft Fakes as a framework that helps isolate code for testing by replacing dependencies with stubs or shims. It provides examples of how to generate and use stubs and shims. In the end, it summarizes when to use stubs versus shims and takes questions from the audience.

Manaual testing training course content

mindqsystems

The training program is designed to give participants the skills & knowledge to gain a competitive advantage in starting / enhancing a career in software testing. Participants receive up-to-date training in multiple areas in Software Testing and a thorough understanding of real-world projects. Successful completion of this program leads to placement assistance and participation in campus placements at Mind Q.

What's hot

Writing Better Tests - Applying Clean-Code TDD at 99designs

lachlandonald

Code Review Matters and Manners

Waterfalls for agile cambridge

Waterfalls for Agile in a bag

АННА ТИМОФІЄВА & СЕРГІЙ МАЛИНОВСЬКИЙ «Tools and Tips of video connection test...

QADay

Presentation delex

Alexander Pushkarev

TDD - Christchurch APN May 2012

Alan Christensen

Babysitting your orm essenmacher, adam

Adam Essenmacher

Increase selenium tests stability via java script

How to get the most out of code reviews

JavaDayUA

RoboCon 2018: How did we get here? Where do we go next?

Pekka Klärck

Model Driven Developing & Model Based Checking: Applying Together

Iosif Itkin

UK star ultimate testing survival

Viktor Slavchev

Type mock isolator

MaslowB

Staying Ahead of the Curve

Why test automation projects are failing

The Bumpy Road Towards Continuous Delivery

Benjamin Bischoff

Software testing

Inthra onsap

Writing Tests Effectively

Paul Boocock

What's hot (19)

Writing Better Tests - Applying Clean-Code TDD at 99designs

Code Review Matters and Manners

Waterfalls for agile cambridge

Waterfalls for Agile in a bag

АННА ТИМОФІЄВА & СЕРГІЙ МАЛИНОВСЬКИЙ «Tools and Tips of video connection test...

Presentation delex

TDD - Christchurch APN May 2012

Babysitting your orm essenmacher, adam

Increase selenium tests stability via java script

How to get the most out of code reviews

RoboCon 2018: How did we get here? Where do we go next?

Model Driven Developing & Model Based Checking: Applying Together

UK star ultimate testing survival

Type mock isolator

Staying Ahead of the Curve

Why test automation projects are failing

The Bumpy Road Towards Continuous Delivery

Software testing

Writing Tests Effectively

Similar to Scam2007 jiang

Microsoft Fakes, Unit Testing the (almost) Untestable Code

Unit Tests with Microsoft Fakes

Getting value from IoT, Integration and Data Analytics

Manaual testing training course content

mindqsystems

Cross functional peer review preso 10-01-2013

SmartBear

This document discusses how cross-functional peer review of requirements, design, code, and test plans within agile teams can improve software quality. It presents findings from a case study showing that reviewing 200-500 lines of code per hour while reviewing no more than 400 lines at a time yields the lowest defect density. Industry metrics also show that high-performing teams find fewer defects post-release by extensively testing in development. Benefits of cross-functional peer review include improved communication, faster problem identification, more readable code, and increased sharing of best practices across roles within development teams.

Clipper: A Low-Latency Online Prediction Serving System: Spark Summit East ta...

Spark Summit

Machine learning is being deployed in a growing number of applications which demand real-time, accurate, and robust predictions under heavy query load. However, most machine learning frameworks and systems only address model training and not deployment. In this talk, we present Clipper, a general-purpose low-latency prediction serving system. Interposing between end-user applications and a wide range of machine learning frameworks, Clipper introduces a modular architecture to simplify model deployment across frameworks. Furthermore, by introducing caching, batching, and adaptive model selection techniques, Clipper reduces prediction latency and improves prediction throughput, accuracy, and robustness without modifying the underlying machine learning frameworks. We evaluated Clipper on four common machine learning benchmark datasets and demonstrate its ability to meet the latency, accuracy, and throughput demands of online serving applications. We also compared Clipper to the Tensorflow Serving system and demonstrate comparable prediction throughput and latency on a range of models while enabling new functionality, improved accuracy, and robustness.

TLC2018 Thomas Haver: The Automation Firehose - Be Strategic and Tactical

Anna Royzman

Using MLOps to Bring ML to Production/The Promise of MLOps

Weaveworks

In this final Weave Online User Group of 2019, David Aronchick asks: have you ever struggled with having different environments to build, train and serve ML models, and how to orchestrate between them? While DevOps and GitOps have made huge traction in recent years, many customers struggle to apply these practices to ML workloads. This talk will focus on the ways MLOps has helped to effectively infuse AI into production-grade applications through establishing practices around model reproducibility, validation, versioning/tracking, and safe/compliant deployment. We will also talk about the direction for MLOps as an industry, and how we can use it to move faster, with more stability, than ever before. The recording of this session is on our YouTube Channel here: https://youtu.be/twsxcwgB0ZQ Speaker: David Aronchick, Head of Open Source ML Strategy, Microsoft Bio: David leads Open Source Machine Learning Strategy at Azure. This means he spends most of his time helping humans to convince machines to be smarter. He is only moderately successful at this. Previously, David led product management for Kubernetes at Google, launched GKE, and co-founded the Kubeflow project. David has also worked at Microsoft, Amazon and Chef and co-founded three startups. Sign up for a free Machine Learning Ops Workshop: http://bit.ly/MLOps_Workshop_List Weaveworks will cover concepts such as GitOps (operations by pull request), Progressive Delivery (canary, A/B, blue-green), and how to apply those approaches to your machine learning operations to mitigate risk.

Bottlenecks in Java Applications

GlobalLogic Ukraine

What would Jesus Developer do?

Lukáš Čech

This document discusses applying developer best practices to digital analytics work. It recommends: 1) Using local development with Node.js, build tools, and IDEs to avoid copy-pasting code and work offline. 2) Implementing version control like Git for change history, issue tracking, and teamwork. 3) Writing modular, reusable code through organization conventions and build tools to localize issues. 4) Taking an API-based approach can create a single codebase for multiple properties with continuous integration and auto-generated documentation.

Best Practices for Enterprise Continuous Delivery of Oracle Fusion Middlewa...

Entity Framework: To the Unit of Work Design Pattern and Beyond

Steve Westgarth

The document discusses issues with traditional ASP.NET application architectures and how the introduction of MVC helped address some problems. It then describes how the presenter implemented the Unit of Work pattern to help with testing and database consistency in their application. However, this implementation violated SOLID principles. The presenter improved the design by separating concerns into distinct layers and implementing generic repositories. This made the code more testable and decoupled from Entity Framework while better adhering to object-oriented design principles. In the end, the presenter advocates evaluating design patterns critically and continuously challenging accepted approaches.

Programming languages and techniques for today’s embedded andIoT world

Rogue Wave Software

This presentation looks at the problem of selecting the best programming language and tools to ensure IoT software is secure, robust, and safe. By taking a look at industry best practices and decades of knowledge from other industries (such as automotive and aerospace), you will learn the criteria necessary to choose the right language, how to overcome gaps in developers’ skills, and techniques to ensure your team delivers bulletproof IoT applications.

Slides chapter 3

Hardik Patel

Prescriptive process models attempt to organize the software development life cycle by defining activities, their order, and relationships. Early models like code-and-fix lacked predictability and manageability. Newer models strive for structure and order to achieve coordination, while allowing for changes as more is learned. However, relying solely on prescriptive models may be inappropriate given the need for change in software development.

Slides chapter 3

Priyanka Shetty

Prescriptive process models attempt to organize the software development life cycle by defining activities, their order, and relationships. Early models like code-and-fix lacked predictability and manageability. Newer models strive for structure and order to achieve coordination, while allowing for changes as feedback is received. However, relying solely on prescriptive models may be inappropriate in a world that demands flexibility and change.

SLM (Sample Lifecycle Manager)

limscoder

The University of Arizona Genetics Core (UAGC) provides molecular biology lab services to on-campus researchers, other university scientists, and corporate programs. It processes over 100,000 samples per year through services like sequencing, genotyping, and data analysis. The Sample Lifecycle Manager (SLM) aims to integrate these UAGC services into a complete sample-to-data workflow for customers through features like sample submission and tracking, automated reactions, and result delivery. The second generation of SLM uses a modular Django framework called Eager that is better suited for customizing workflows compared to the first generation's traditional architecture.

Unit test in JavaScript

bmarchal

The document discusses unit testing in JavaScript. It introduces Jasmine as a tool for writing formal executable specifications in JavaScript. Jasmine helps write tests that integrate with development methodologies and provides tools to support testing. Examples of unit tests are provided, showing how to test functions and component interactions. Guidelines for writing testable code according to SOLID principles are also outlined.

Automation Test Framework

Sachin-QA

In this session you will learn: Introduction to Test Automation Framework What is a Test Automation Framework? Utility of Test Automation Framework Sample Automation Test Framework Types of Automation Frameworks Data Driven Automation Framework Keyword Driven Automation Framework Hybrid Automation Framework Benefits of Automation Framework Approach For more information: https://www.mindsmapped.com/courses/quality-assurance/qa-software-testing-training-for-beginners/

Vs2010 alm overview 22nd march

Spiffy

This document discusses application lifecycle management (ALM) using Visual Studio 2010. It notes common pitfalls that can occur without proper ALM such as broken builds, poor quality, and integration issues. The document outlines the three domains of ALM: governance, implementation, and operations. It then highlights features in Visual Studio 2010 and Team Foundation Server that enable ALM, including requirements and task management, source control, unit testing, code analysis, load testing, and integration with SQL Server and SharePoint.

5 Steps to Jump Start Your Test Automation

Sauce Labs

With the acceleration of software creation and delivery, test activities must align to the new tempo. Developers need immediate feedback to be efficient and correct defects as those are introduced. The path to achieving this vision is to build a reliable and scalable continuous test solution. All beginnings are hard. Having a well-defined plan outlining the approach for your organization to create test automation is key to ensure long term success. Join Diego Molina, Senior Software Engineer at Sauce Labs as he discusses: The importance of setting up the team correctly from the start Choosing the right Testing Framework for your organization Identifying the right scenarios and workflows to test Learning to avoid common pitfalls at the beginning of the transformation journey

Selenium web driver_2.0_presentation

sayhi2sudarshan

Similar to Scam2007 jiang (20)

Microsoft Fakes, Unit Testing the (almost) Untestable Code

Unit Tests with Microsoft Fakes

Manaual testing training course content

Cross functional peer review preso 10-01-2013

Clipper: A Low-Latency Online Prediction Serving System: Spark Summit East ta...

TLC2018 Thomas Haver: The Automation Firehose - Be Strategic and Tactical

Using MLOps to Bring ML to Production/The Promise of MLOps

Bottlenecks in Java Applications

What would Jesus Developer do?

Best Practices for Enterprise Continuous Delivery of Oracle Fusion Middlewa...

Entity Framework: To the Unit of Work Design Pattern and Beyond

Programming languages and techniques for today’s embedded andIoT world

Slides chapter 3

SLM (Sample Lifecycle Manager)

Unit test in JavaScript

Automation Test Framework

Vs2010 alm overview 22nd march

5 Steps to Jump Start Your Test Automation

Selenium web driver_2.0_presentation

More from SAIL_QU

Studying the Integration Practices and the Evolution of Ad Libraries in the G...

In-app advertisements have become a major revenue for app developers in the mobile app economy. Ad libraries play an integral part in this ecosystem as app developers integrate these libraries into their apps to display ads. However, little is known about how app developers integrate these libraries with their apps and how these libraries have evolved over time. In this thesis, we study the ad library integration practices and the evolution of such libraries. To understand the integration practices of ad libraries, we manually study apps and derive a set of rules to automatically identify four strategies for integrating multiple ad libraries. We observe that integrating multiple ad libraries commonly occurs in apps with a large number of downloads and ones in categories with a high percentage of apps that display ads. We also observe that app developers prefer to manage their own integrations instead of using off the shelf features of ad libraries for integrating multiple ad libraries. To study the evolution of ad libraries, we conduct a longitudinal study of the 8 most popular ad libraries. In particular, we look at their evolution in terms of size, the main drivers for releasing a new ad library version, and their architecture. We observe that ad libraries are continuously evolving with a median release interval of 34 days. Some ad libraries have grown exponentially in size (e.g., Facebook Audience Network ad library), while other libraries have worked to reduce their size. To study the main drivers for releasing an ad library version, we manually study the release notes of the eight studied ad libraries. We observe that ad library developers continuously update their ad libraries to support a wider range of Android versions (i.e., to ensure that more devices can use the libraries without errors). Finally, we derive a reference architecture for ad libraries and study how the studied ad libraries diverged from this architecture during our study period. Our findings can assist ad library developers to understand the challenges for developing ad libraries and the desired features of these libraries.

Studying the Dialogue Between Users and Developers of Free Apps in the Google...

Improving the testing efficiency of selenium-based load tests

Studying User-Developer Interactions Through the Distribution and Reviewing M...

This document discusses studying user-developer interactions through the distribution and reviewing mechanisms of the Google Play Store. It analyzes emergency updates made by developers to fix issues, the dialogue between users and developers through reviews and responses, and how the reviewing mechanism can help identify good and bad updates. The study found that responding to reviews is six times more likely to increase an app's rating, with 84% of rating increases going to four or five stars. Three common patterns of developer responses were identified: responding to negative or long reviews, only negative reviews, and reviews shortly after an update.

Studying online distribution platforms for games through the mining of data f...

Our studies of Steam platform data provided insights into online game distribution: 1) Urgent game updates were used to fix crashes, balance issues, and functionality; frequent updaters released more 0-day patches. 2) The Early Access model attracted indie developers and increased game participation; reviews were more positive during Early Access. 3) Game reviews were typically short and in English; sales increased review volume more than new updates; negative reviews came after longer play.

Understanding the Factors for Fast Answers in Technical Q&A Websites: An Empi...

This study analyzed factors that impact the speed of questions receiving accepted answers on four popular Stack Exchange websites: Stack Overflow, Mathematics, Ask Ubuntu, and Super User. The researchers examined question, answerer, asker, and answer factors from over 150,000 questions. They built classification models and found that key factors for fast answers included the past speed of answerers, length of the question, and past speed of answers for the question's tags. The models achieved AUCs of 0.85-0.95. Fast answers relied heavily on answerers, especially frequent answerers. The study suggests improving incentives for non-frequent and more difficult questions to attract diverse answerers.

Investigating the Challenges in Selenium Usage and Improving the Testing Effi...

Selenium is a popular tool for browser-based automation testing. The author analyzes challenges in using Selenium by mining Selenium questions on Stack Overflow. Programming language-related questions, especially for Java and Python, are most common and growing fastest. Less than half of questions receive accepted answers, and questions about browsers and components take longest. In the second part, the author develops an approach to improve efficiency of Selenium-based load testing by sharing browsers among user instances. This increases the number of error-free users by 20-22% while reducing memory usage.

Mining Development Knowledge to Understand and Support Software Logging Pract...

This document summarizes Heng Li's PhD thesis on mining development knowledge to understand and support software logging practices. It discusses how logging code is used to record runtime information but can be difficult for developers to maintain. The thesis aims to understand current logging practices and develop tools by mining change history, source code, issue reports, and other development knowledge. It presents research that analyzes logging-related issues to identify developers' logging concerns, uses code topics and structure to predict where logging statements should be added, leverages code changes to suggest when logging code needs updating, and applies machine learning models to recommend appropriate log levels.

Which Log Level Should Developers Choose For a New Logging Statement?

The document discusses choosing an appropriate log level when adding a new logging statement. It finds that an ordinal regression model can effectively model log levels, achieving an AUC of 0.76-0.81 in within-project evaluation and 0.71-0.8 in cross-project evaluation. The most influential factors for determining log levels vary between projects and include metrics related to the logging statement, containing code block, and file as well as code change and historical change metrics.

Towards Just-in-Time Suggestions for Log Changes

The document presents a study on providing just-in-time suggestions for log changes when developers make code changes. The researchers analyzed over 32,000 log changes from 4 systems. They found 20 reasons for log changes that fall into 4 categories: block changes, log improvements, dependence-driven changes, and logging issues. A random forest classifier using 25 software metrics related to code changes, history, and complexity achieved 0.84-0.91 AUC in predicting whether a log change is needed. Change metrics and product metrics were the most influential factors. The study aims to help developers make better logging decisions for failure diagnosis.

The Impact of Task Granularity on Co-evolution Analyses

The document discusses how task granularity at different levels (e.g. commits, pull requests, work items) can impact analyses of co-evolution in software projects. It finds that analyzing at the commit-level can overlook relationships between tasks that span multiple commits. Work item level analysis is recommended to provide a more complete view of co-evolution, as median of 29% of work items consist of multiple commits, and analyzing at the commit level would miss 24% of co-changed files and inability to group 83% of related commits.

A Framework for Evaluating the Results of the SZZ Approach for Identifying Bu...

How are Discussions Associated with Bug Reworking? An Empirical Study on Open...

1) Initial bug fix discussions with more comments and more developers participating are more likely to experience later bug reworking through re-opening or re-patching of the bug. 2) Manual analysis found that defective initial fixes and failure to reach consensus in discussions contributed to later reworking. 3) For re-opened bugs, initial discussions focused on addressing a particular problem through a burst of comments, while re-patched bugs lacked thorough code review and testing during the initial fix period.

A Study of the Relation of Mobile Device Attributes with the User-Perceived Q...

This study examined the relationship between mobile device attributes and user-perceived quality of Android apps. The researchers analyzed 150,373 star ratings from Google Play across 30 devices and 280 apps. They found that the perceived quality of apps varies across devices, and having better characteristics of an attribute does not necessarily correlate with higher quality. Device OS version, resolution, and CPU showed significant relationships with ratings, as did some app attributes like lines of code and number of inputs. However, some device attributes had stronger relationships than app attributes.

A Large-Scale Study of the Impact of Feature Selection Techniques on Defect C...

This document presents the results of a large-scale study on the impact of feature selection techniques on defect classification models. The study used expanded scopes including multiple datasets from NASA and PROMISE with different feature types, more classification techniques from different paradigms, and additional feature selection techniques. The results show that correlation-based feature subset selection techniques like FS1 and FS2 consistently appear in the top ranks across most of the datasets, projects within the datasets, and classification techniques. The document concludes that future defect classification studies should consider applying correlation-based feature selection techniques.

Studying the Dialogue Between Users and Developers of Free Apps in the Google...

The study analyzes user-developer interactions through reviews and responses on the Google Play Store. It finds that responding to reviews has a significant positive impact, with 84% of rating increases due to the developer addressing the issue or providing guidance. Three common response patterns were identified: only negative reviews, negative or longer reviews, and reviews shortly after an update. Developers most often thank the user, ask for details, provide guidance, or ask for an endorsement. Guidance responses can address common issues through FAQs. The analysis considered over 2,000 apps, 355,000 review changes, 128,000 responses, and 4 million reviews.

What Do Programmers Know about Software Energy Consumption?

This document summarizes the results of a survey of 122 programmers about their knowledge of software energy consumption. The survey found that programmers have limited awareness of energy consumption and how to reduce it. They were unaware of the main causes of high energy usage. Programmers lacked knowledge about how to properly rank the energy consumption of different hardware components and were unfamiliar with strategies to improve efficiency, such as minimizing I/O and avoiding polling. The study concludes that programmers would benefit from more education on software energy usage and its causes.

Threshold for Size and Complexity Metrics: A Case Study from the Perspective ...

Revisiting the Experimental Design Choices for Approaches for the Automated R...

Prior research on automated duplicate issue report retrieval focused on improving performance metrics like recall rate. The author revisits experimental design choices from four perspectives: needed effort, data changes, data filtration, and evaluation process. The thesis contributions are: 1) Showing the importance of considering needed effort in performance measurement. 2) Proposing a "realistic evaluation" approach and analyzing prior findings with it. 3) Developing a genetic algorithm to filter old issue reports and improve performance. 4) Highlighting the impact of "just-in-time" features on evaluation. The findings help better understand benefits and limitations of prior work in this area.

Measuring Program Comprehension: A Large-Scale Field Study with Professionals