The document characterizes the verification process for bug fixes in two open source IDEs by mining their bug repositories. It finds that around 20% of developers perform over 80% of verifications, which tend to occur in bursts after releases. Most verification comments do not specify the technique used. The analysis risks being biased by mass verifications for cleanup and pseudo-verifications where the label does not truly mean the fix was verified. Future work involves modeling the verification process and its effects as a causal network.
Here are all the 6 winning stories of the week - The Law of Sacrifice. The stories are in the sequence of 1st prize winning stories to consolation prize winning stories. I also request you to please read these beautiful stories and comment on the stories. Thanks
Addressing the issue of mortgage arrears in Ireland: a good practice guide fr...HML Ltd
This good practice white paper details HML’s experience of managing mortgage arrears in Ireland, with our main focus on ensuring the most sustainable outcomes for customers. With banks in the country currently under increasing pressure from the Central Bank of Ireland (CBI) to not only propose sustainable solutions to customers, but to also complete deals, a significant amount of resources will need putting into arrears management and collections. Not every bank, mortgage portfolio owner or other stakeholders may have the capacity to ramp up customer contact and collections, which is where HML can prove to be of assistance. We have been servicing Irish lenders’ loan portfolios since 2005 and have in-depth knowledge and experience of Ireland’s unique financial environment, making us ideally situated to help banks meet their CBI targets.
At HML, we believe Standard Financial Statement (SFS) engagement with the borrower should be at the heart of any successful arrears management strategy, as this is the gateway to the Mortgage Arrears Resolution Process (MARP). Once within MARP, mortgage customers can evidence they are engaging with their lender, which – to a point – protects the borrower from repossession. Cash collection also increases when a customer is within MARP, which is beneficial to both the borrower and their lender.
This white paper will take you through the process of managing Irish mortgage accounts in arrears, from ensuring SFS completion and engaging with MARP to sustainable restructures and the next steps lenders need to take in order to meet their CBI targets. We will draw upon our experience and provide a case study as an example of where a client has seen considerable success after HML supported its arrears management strategy and collections operations.
Here are all the 6 winning stories of the week - The Law of Sacrifice. The stories are in the sequence of 1st prize winning stories to consolation prize winning stories. I also request you to please read these beautiful stories and comment on the stories. Thanks
Addressing the issue of mortgage arrears in Ireland: a good practice guide fr...HML Ltd
This good practice white paper details HML’s experience of managing mortgage arrears in Ireland, with our main focus on ensuring the most sustainable outcomes for customers. With banks in the country currently under increasing pressure from the Central Bank of Ireland (CBI) to not only propose sustainable solutions to customers, but to also complete deals, a significant amount of resources will need putting into arrears management and collections. Not every bank, mortgage portfolio owner or other stakeholders may have the capacity to ramp up customer contact and collections, which is where HML can prove to be of assistance. We have been servicing Irish lenders’ loan portfolios since 2005 and have in-depth knowledge and experience of Ireland’s unique financial environment, making us ideally situated to help banks meet their CBI targets.
At HML, we believe Standard Financial Statement (SFS) engagement with the borrower should be at the heart of any successful arrears management strategy, as this is the gateway to the Mortgage Arrears Resolution Process (MARP). Once within MARP, mortgage customers can evidence they are engaging with their lender, which – to a point – protects the borrower from repossession. Cash collection also increases when a customer is within MARP, which is beneficial to both the borrower and their lender.
This white paper will take you through the process of managing Irish mortgage accounts in arrears, from ensuring SFS completion and engaging with MARP to sustainable restructures and the next steps lenders need to take in order to meet their CBI targets. We will draw upon our experience and provide a case study as an example of where a client has seen considerable success after HML supported its arrears management strategy and collections operations.
Dealing fairly with interest-only customers; a good practice guide from HML -...HML Ltd
Since the original version of our Interest-Only Good Practice Guide, the Financial Conduct Authority has published its finalised guidance into interest-only mortgages. This latest version contains the updates between the thematic review and the finalised guidance to help you shape your customer communication strategies.
If you’re considering NIH’s R15 grant, there are some facts you should know before you apply — including what the grant is, who is eligible to receive it, and what reviewers look for in R15 applications.
NIH designed the R15, or Academic Research Enhancement Award (AREA), to support biomedical and behavioral sciences research at small health professional schools. The grant aims to expose graduate and undergraduate students to scientific investigation and bolster the research environment at these smaller institutions.
There have been a number of new developments this year. Christina discusses new federal and state initiatives, new case law and other developments that directly affect employers.
Obtaining an R01 award where you are the principal investigator, and delivering on the Aims of that proposal, are absolutely essential in your quest to build a scientific reputation. This is essential to encourage experts in your field to write supportive tenure letters.
This information-packed Webinar will focus on detailed strategies for capturing that first R01: a cornerstone of your career.
Employers need to be aware that decisions they are making now about the size and make-up of their workforce will affect whether they exceed the 50 employee threshold that triggers the "pay or play" penalty in the Affordable Care Act. This presentation will focus on strategies for avoiding or minimizing exposure to the penalties under the Act.
Семейное образование и образование будущегоfpolicy_ru
Доклад генерального директора АЦ "Семейная политика.РФ" Павла Парфентьева на Конференции «Поддержка субъектности в учебной деятельности: от концептуальных идей к конкретной практике» 12-13 июня, Санкт-Петербург.
Docker on a local machine and Docker in production — are two big differences. It's easy to play with technology but it's hard to do something real for many customers.
Half a year ago inside of Alpha Laboratory (division of Alfa-Bank) we've started building new microservices architecture for one of our pilot projects. We've almost completely changed a stack of the used technologies on a frontend and significantly changed it on a middle layer. For package and distribution we have choosen Docker. Two months ago we've deployed project to production and have opened service for clients.
In the report the following topics will be covered:
- reasons of a choice Docker;
- why Docker without other tools is not enough for a production;
- what stack of technologies we used in our solution;
- what advantages we've got;
- what problems have been faced and how we've solved them.
Vskills certification for The Grinder Testing Professional assesses the candidate as per the company’s need for load testing web applications. The certification tests the candidates on various areas in agents, workers, properties file, logging, console, TCPProxy, scripts, Jython, Clojure, instrumentation, script gallery, plug-ins, statistics, SSL and garbage collection.
Dealing fairly with interest-only customers; a good practice guide from HML -...HML Ltd
Since the original version of our Interest-Only Good Practice Guide, the Financial Conduct Authority has published its finalised guidance into interest-only mortgages. This latest version contains the updates between the thematic review and the finalised guidance to help you shape your customer communication strategies.
If you’re considering NIH’s R15 grant, there are some facts you should know before you apply — including what the grant is, who is eligible to receive it, and what reviewers look for in R15 applications.
NIH designed the R15, or Academic Research Enhancement Award (AREA), to support biomedical and behavioral sciences research at small health professional schools. The grant aims to expose graduate and undergraduate students to scientific investigation and bolster the research environment at these smaller institutions.
There have been a number of new developments this year. Christina discusses new federal and state initiatives, new case law and other developments that directly affect employers.
Obtaining an R01 award where you are the principal investigator, and delivering on the Aims of that proposal, are absolutely essential in your quest to build a scientific reputation. This is essential to encourage experts in your field to write supportive tenure letters.
This information-packed Webinar will focus on detailed strategies for capturing that first R01: a cornerstone of your career.
Employers need to be aware that decisions they are making now about the size and make-up of their workforce will affect whether they exceed the 50 employee threshold that triggers the "pay or play" penalty in the Affordable Care Act. This presentation will focus on strategies for avoiding or minimizing exposure to the penalties under the Act.
Семейное образование и образование будущегоfpolicy_ru
Доклад генерального директора АЦ "Семейная политика.РФ" Павла Парфентьева на Конференции «Поддержка субъектности в учебной деятельности: от концептуальных идей к конкретной практике» 12-13 июня, Санкт-Петербург.
Docker on a local machine and Docker in production — are two big differences. It's easy to play with technology but it's hard to do something real for many customers.
Half a year ago inside of Alpha Laboratory (division of Alfa-Bank) we've started building new microservices architecture for one of our pilot projects. We've almost completely changed a stack of the used technologies on a frontend and significantly changed it on a middle layer. For package and distribution we have choosen Docker. Two months ago we've deployed project to production and have opened service for clients.
In the report the following topics will be covered:
- reasons of a choice Docker;
- why Docker without other tools is not enough for a production;
- what stack of technologies we used in our solution;
- what advantages we've got;
- what problems have been faced and how we've solved them.
Vskills certification for The Grinder Testing Professional assesses the candidate as per the company’s need for load testing web applications. The certification tests the candidates on various areas in agents, workers, properties file, logging, console, TCPProxy, scripts, Jython, Clojure, instrumentation, script gallery, plug-ins, statistics, SSL and garbage collection.
Coding Naked – Practical steps to moving towards & embracing TDD. We'll overview the normal roadblocks that people typically run in to, and practical ways to overcome those road blocks on your way to embracing Test Driven Development - make coding without tests as uncomfortable as coding naked!
Agile Open Source Performance Testing Workshop for Business ManagersClever Moe
Use Selenium, soapUI, Sahi, TestMaker Performance Testing In Your Organization. These are slides from a free Webinar titled "The Agile Open Source Way To Load Test, Scalability Test, and Stress Test In Your Organization". Your organization may have adopted Agile Software Development Methodology and forgot about load and performance testing! Learn the Open Source Testing way to load and performance test your Web applications, Rich Internet Applications (RIA, using Ajax, Flex, Flash, Oracle Forms, Applets,) and SOAP and REST Web services. This free Webinar delivers a testing methodology, tools, and best/worst practices.
5 Tips for Agile Mobile App Security TestingNowSecure
Originally Presented March 21, 2018
Most mobile app penetration tests or vulnerability assessments take anywhere from a couple of days to two weeks to deliver because of the manual approaches, brittle open source stacks in homegrown testing rigs and legacy application security testing (AST) tools. The shift to agile development common in mobile app development teams has left appsec testing behind. New mobile app builds are pushed daily, weekly or monthly, and appsec testing teams struggle to keep up. Each new build brings new code, including 3rd-party libraries, and with that code comes new potential vulnerabilities.
Application security & testing teams - this one’s for you. If you’re looking for ways to join the agile approach and keep pace with the speed of your development team’s CI/CD pipeline, take stock of these 5 tips for mobile appsec testing and integrate them into your company’s workflow.
If you are building a commercial Force.com app with a team of developers, this session is for you. Join us to learn best practices for setting up your Force.com IDE, managing source code, creating automated builds, deploying to test environments, and more. Hear from a panel of seasoned ISVs who are employing key team development principles. This session is primarily for product managers, architects, and developers (isvpartners).
Peer Code Review: In a Nutshell and The Tantric Team: Getting Your Automated ...Atlassian
Peer Code Review: In a Nutshell
Development is inherently collaborative. So why aren't you doing code review? This session discusses the importance of collaboration around your source code, the impact code review can have on development teams, and offers guidance on how to get started.
Atlassian Speaker: Matt Quail
Customer Speaker: Patrick Coleman of Dash
Key Takeaways:
* Peer code review explained
* Benefits and approaches to effective code review
The Tantric Team: Getting Your Automated Build Groove On
Want to take your build automation to the next level? This session explains the process of setting up an automated software development infrastructure using the Atlassian tools, focusing on continuous integration. This session outlines key steps involved in automating a typical Java project using Ant, Bamboo, FishEye, Clover, JIRA and a large cast of other supporting tools.
Customer Speaker: Rik Tamm-Daniels
Key Takeaways:
* Continuous integration how-to
* Integrating multiple Atlassian tools, along with other development infrastructure
Similar to Characterizing Verification of Bug Fixes in Two Open Source IDEs (MSR 2012) (20)
R é uma linguagem gratuita, poderosa e rápida para análise e visualização de dados. Tire suas próprias conclusões! Mini-palestra apresentada no CPDx (Ciclo de Palestras para Desenvolvedores) na UFBA em 16/01/2013
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
20 Comprehensive Checklist of Designing and Developing a WebsitePixlogix Infotech
Dive into the world of Website Designing and Developing with Pixlogix! Looking to create a stunning online presence? Look no further! Our comprehensive checklist covers everything you need to know to craft a website that stands out. From user-friendly design to seamless functionality, we've got you covered. Don't miss out on this invaluable resource! Check out our checklist now at Pixlogix and start your journey towards a captivating online presence today.
Building RAG with self-deployed Milvus vector database and Snowpark Container...Zilliz
This talk will give hands-on advice on building RAG applications with an open-source Milvus database deployed as a docker container. We will also introduce the integration of Milvus with Snowpark Container Services.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Characterizing Verification of Bug Fixes in Two Open Source IDEs (MSR 2012)
1. Characterizing
Verification of Bug Fixes
in Two Open Source IDEs
Rodrigo Souza* and Christina Chavez
Software Engineering Labs
Department of Computer Science - IM
Universidade Federal da Bahia (UFBA), Brazil
{rodrigo, flach}@dcc.ufba.br
* speaker
June 2, 2012
MSR 2012, Zürich
30.
Mass verifications: represent
repository cleanup, not software
verification.
They may represent a large part of the
verifications and bias your analyses.
18
31.
Pseudo verifications: In some
projects, marking a bug as VERIFIED
means something else!
(e.g., in Eclipse/EMF, since 2007, it
means that the fix is available in a build)
19
34. process
verification
process*
product
(software)
* qa team, reopening
verification phase etc.
22
35. causal
process (bayesian)
network
verification
process*
product
(software)
* qa team, reopening
verification phase etc.
22
36. Thanks!
Verification
✓ ✗
phase
QA team ✗ ✓
Comments rarely state the verification technique.
Beware of mass verifications and pseudo verifications.
23
Editor's Notes
\n
First of all, this is how a bug report works.\nFirst someone reports a new bug.\nAfter some discussion, a developer submits a bug fix for the problem, and marks the bug as FIXED.\nThen, someone else verifies that the bug fix is appropriate, and marks the bug as VERIFIED.\n
First of all, this is how a bug report works.\nFirst someone reports a new bug.\nAfter some discussion, a developer submits a bug fix for the problem, and marks the bug as FIXED.\nThen, someone else verifies that the bug fix is appropriate, and marks the bug as VERIFIED.\n
First of all, this is how a bug report works.\nFirst someone reports a new bug.\nAfter some discussion, a developer submits a bug fix for the problem, and marks the bug as FIXED.\nThen, someone else verifies that the bug fix is appropriate, and marks the bug as VERIFIED.\n
First of all, this is how a bug report works.\nFirst someone reports a new bug.\nAfter some discussion, a developer submits a bug fix for the problem, and marks the bug as FIXED.\nThen, someone else verifies that the bug fix is appropriate, and marks the bug as VERIFIED.\n
First of all, this is how a bug report works.\nFirst someone reports a new bug.\nAfter some discussion, a developer submits a bug fix for the problem, and marks the bug as FIXED.\nThen, someone else verifies that the bug fix is appropriate, and marks the bug as VERIFIED.\n
First of all, this is how a bug report works.\nFirst someone reports a new bug.\nAfter some discussion, a developer submits a bug fix for the problem, and marks the bug as FIXED.\nThen, someone else verifies that the bug fix is appropriate, and marks the bug as VERIFIED.\n
In this exploratory work, we try to characterize the process of verifying bug fixes by mining bug repositories.\nWe investigated three questions: when are bug fixes verified? who verifies them? and how are them verified?\n\n
In this exploratory work, we try to characterize the process of verifying bug fixes by mining bug repositories.\nWe investigated three questions: when are bug fixes verified? who verifies them? and how are them verified?\n\n
In this exploratory work, we try to characterize the process of verifying bug fixes by mining bug repositories.\nWe investigated three questions: when are bug fixes verified? who verifies them? and how are them verified?\n\n
In this exploratory work, we try to characterize the process of verifying bug fixes by mining bug repositories.\nWe investigated three questions: when are bug fixes verified? who verifies them? and how are them verified?\n\n
In this exploratory work, we try to characterize the process of verifying bug fixes by mining bug repositories.\nWe investigated three questions: when are bug fixes verified? who verifies them? and how are them verified?\n\n
In this exploratory work, we try to characterize the process of verifying bug fixes by mining bug repositories.\nWe investigated three questions: when are bug fixes verified? who verifies them? and how are them verified?\n\n
We used data from the previous MSR Challenge, containing about 10 years of bug reports from two open source IDEs: Eclipse and NetBeans. We analyzed two subprojects for each IDE.\n
So, first, when are bug fixes verified?\n
We have plotted the accumulated number of verifications over time for the projects.\nFor NetBeans, the verification rate is almost constant, meaning that bug fixes are verified all the time.\n\n
We have plotted the accumulated number of verifications over time for the projects.\nFor NetBeans, the verification rate is almost constant, meaning that bug fixes are verified all the time.\n\n
We have plotted the accumulated number of verifications over time for the projects.\nFor NetBeans, the verification rate is almost constant, meaning that bug fixes are verified all the time.\n\n
We have plotted the accumulated number of verifications over time for the projects.\nFor NetBeans, the verification rate is almost constant, meaning that bug fixes are verified all the time.\n\n
We have plotted the accumulated number of verifications over time for the projects.\nFor NetBeans, the verification rate is almost constant, meaning that bug fixes are verified all the time.\n\n
For Eclipse/Platform, however, verifications are much more frequent just before a release,\nwhich suggests that there’s a verification phase in Eclipse’s process.\n
For Eclipse/Platform, however, verifications are much more frequent just before a release,\nwhich suggests that there’s a verification phase in Eclipse’s process.\n
For Eclipse/Platform, however, verifications are much more frequent just before a release,\nwhich suggests that there’s a verification phase in Eclipse’s process.\n
For Eclipse/Platform, however, verifications are much more frequent just before a release,\nwhich suggests that there’s a verification phase in Eclipse’s process.\n
For Eclipse/Platform, however, verifications are much more frequent just before a release,\nwhich suggests that there’s a verification phase in Eclipse’s process.\n
For Eclipse/Platform, however, verifications are much more frequent just before a release,\nwhich suggests that there’s a verification phase in Eclipse’s process.\n
For Eclipse/Platform, however, verifications are much more frequent just before a release,\nwhich suggests that there’s a verification phase in Eclipse’s process.\n
For Eclipse/Platform, however, verifications are much more frequent just before a release,\nwhich suggests that there’s a verification phase in Eclipse’s process.\n
Next, who verifies the bug fixes? In some projects, there is a team dedicated to verifications: Quality Assurance team, or QA team.\n
We defined that the QA team of a project is formed by all developers that perform at least 10 times more verifications than bug fixes.\n
Using this definition, we found that in NetBeans the QA team contains 20% of its developers, who perform more than 80% of the verifications.\n
Using this definition, we found that in NetBeans the QA team contains 20% of its developers, who perform more than 80% of the verifications.\n
Using this definition, we found that in NetBeans the QA team contains 20% of its developers, who perform more than 80% of the verifications.\n
Using this definition, we found that in NetBeans the QA team contains 20% of its developers, who perform more than 80% of the verifications.\n
Using this definition, we found that in NetBeans the QA team contains 20% of its developers, who perform more than 80% of the verifications.\n
In Eclipse, we found no evidence of a QA team.\n
Finally, how are the bug fixes verified?\nThat is, what are the techniques used to verify each bug fix?\n
We looked at the comments developers write when they mark a bug as VERIFIED.\n
But it appears that most comments just state the obvious: that the bug fix was verified using some version of the software.\nUsing regular expressions, we found that less than 4% of the comments refer to automated testing or code inspection, although further research is needed.\n
We’d also like to share some pitfalls we’ve found during this research.\n
Plotting the number of verifications in NetBeans/Platform over its lifetime, we found what appears to be a huge verification effort, represented by a big rise in the graph.\nHowever, by looking at the data, we discovered that this big rise represents...\n\n
More than 2 thousand bugs that were verified... in just 5 hours... by only 1 guy!\nOf course, no human being can do that.\nThe developer was not actually verifying the bug fixes. It turns out, Superman was just doing some cleanup by marking old bugs as verified.\n\n2003-07-01, 2676 bugs, user 17822, 2003-07-01 10:52:14 to 2003-07-01 16:08:14 (about 5 hours)\n
More than 2 thousand bugs that were verified... in just 5 hours... by only 1 guy!\nOf course, no human being can do that.\nThe developer was not actually verifying the bug fixes. It turns out, Superman was just doing some cleanup by marking old bugs as verified.\n\n2003-07-01, 2676 bugs, user 17822, 2003-07-01 10:52:14 to 2003-07-01 16:08:14 (about 5 hours)\n
More than 2 thousand bugs that were verified... in just 5 hours... by only 1 guy!\nOf course, no human being can do that.\nThe developer was not actually verifying the bug fixes. It turns out, Superman was just doing some cleanup by marking old bugs as verified.\n\n2003-07-01, 2676 bugs, user 17822, 2003-07-01 10:52:14 to 2003-07-01 16:08:14 (about 5 hours)\n
So, be careful: mass verifications may represent a large part of the verifications in a project, but they are not really software verification and may bias your analyses.\nIn the previous analyses, mass verifications were discarded.\n\n-- Be careful, because such mass verifications may bias your analyses\n
Also, by reading a few comments, we found that, in some projects, marking a bug as VERIFIED has a special meaning. \nFor example, in Eclipse/EMF it just means that the bug fix was made available in a build).\n\n
Future work\n
People say that, if you control your process, you can control the quality of your product. \n
So we want to investigate how particular features of the bug verification process may influence (directly or indirectly) the reopening of bugs.\n For example, is it more effective to have a verification phase or to verify bug fixes all the time?\n\nWe intend to build a causal network to investigate this question, so we are looking for variables that influence the verification process or the reopening of bugs.\n
So we want to investigate how particular features of the bug verification process may influence (directly or indirectly) the reopening of bugs.\n For example, is it more effective to have a verification phase or to verify bug fixes all the time?\n\nWe intend to build a causal network to investigate this question, so we are looking for variables that influence the verification process or the reopening of bugs.\n
So we want to investigate how particular features of the bug verification process may influence (directly or indirectly) the reopening of bugs.\n For example, is it more effective to have a verification phase or to verify bug fixes all the time?\n\nWe intend to build a causal network to investigate this question, so we are looking for variables that influence the verification process or the reopening of bugs.\n
So we want to investigate how particular features of the bug verification process may influence (directly or indirectly) the reopening of bugs.\n For example, is it more effective to have a verification phase or to verify bug fixes all the time?\n\nWe intend to build a causal network to investigate this question, so we are looking for variables that influence the verification process or the reopening of bugs.\n
So we want to investigate how particular features of the bug verification process may influence (directly or indirectly) the reopening of bugs.\n For example, is it more effective to have a verification phase or to verify bug fixes all the time?\n\nWe intend to build a causal network to investigate this question, so we are looking for variables that influence the verification process or the reopening of bugs.\n
So we want to investigate how particular features of the bug verification process may influence (directly or indirectly) the reopening of bugs.\n For example, is it more effective to have a verification phase or to verify bug fixes all the time?\n\nWe intend to build a causal network to investigate this question, so we are looking for variables that influence the verification process or the reopening of bugs.\n
So we want to investigate how particular features of the bug verification process may influence (directly or indirectly) the reopening of bugs.\n For example, is it more effective to have a verification phase or to verify bug fixes all the time?\n\nWe intend to build a causal network to investigate this question, so we are looking for variables that influence the verification process or the reopening of bugs.\n
So we want to investigate how particular features of the bug verification process may influence (directly or indirectly) the reopening of bugs.\n For example, is it more effective to have a verification phase or to verify bug fixes all the time?\n\nWe intend to build a causal network to investigate this question, so we are looking for variables that influence the verification process or the reopening of bugs.\n
So we want to investigate how particular features of the bug verification process may influence (directly or indirectly) the reopening of bugs.\n For example, is it more effective to have a verification phase or to verify bug fixes all the time?\n\nWe intend to build a causal network to investigate this question, so we are looking for variables that influence the verification process or the reopening of bugs.\n
So we want to investigate how particular features of the bug verification process may influence (directly or indirectly) the reopening of bugs.\n For example, is it more effective to have a verification phase or to verify bug fixes all the time?\n\nWe intend to build a causal network to investigate this question, so we are looking for variables that influence the verification process or the reopening of bugs.\n