DOCSLIB.ORG

Quality-Aware Tooling

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Quality-Aware Tooling source: https://doi.org/10.24442/boristheses.822 | downloaded: 7.10.2021 Quality-Aware Tooling Yuriy Tymchuk Quality-Aware Tooling Inauguraldissertation der Philosophisch-naturwissenschaftlichen Fakultät der Universität Bern vorgelegt von Yuriy Tymchuk von Ukraine Leiter der Arbeit: Prof. Dr. O. Nierstrasz Institut für Informatik Universität Bern This dissertation can be downloaded from scg.unibe.ch. Copyright ©2017 by Yuriy Tymchuk yuriy.tymch.uk The contents of this book are licensed under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license. You are free: to Share — copy and redistribute the material in any medium or format; to Adapt — remix, transform, and build upon the material for any purpose, even commercially. Under the following conditions: Attribution. You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. Share Alike. If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original. The full license is available at https://creativecommons.org/licenses/by-sa/4.0/ Attribution–ShareAlike ISBN: 978-0-244-05081-8 First edition, November 2017 Acknow ledgem ents While this dissertation is just one small step for mankind, it is one giant leap for me. I sincerely thank everyone who supported me on this journey. Although it is nearly impossible to mention every individual who contributed to my Ph.D. experience, I will do my best in the following acknowledgments. *** First of all, I want to express my gratitude to Oscar Nierstrasz who gave me an opportunity to work at the Software Composition Group in gorgeous Bern and who saved my doctoral studies. I thank him for his patience and tolerance for my mistakes, proofreading the papers that had to be ready “for yesterday,” and for the guidance on my Ph.D. trail. I will always admire the way Oscar managed to organize the work in our group and keep track of everything possible. I am going to miss the coffee-break puzzles and the rubber chicken. I am grateful to Radu Marinescu for accepting to be on my Ph.D. committee and for reviewing this dissertation. I thank Paolo Favaro for accepting to chair the examination. I was lucky to spend a couple of years surrounded by smart, fun and friendly members of the Software Composition Group. Big thanks to Andrei for inspiring me with his work and his thesis, Jan for discussing exciting ideas (and letting me know that my Google calendar issue will not be fixed), and Boris for inserting fun transitions between my context switches. Thank you, Manuel, for building Randi, supervising Radi, being a great travel companion, and proofreading this dissertation in a turbo-mode. I am grateful to Nevena who is always caring when it comes to important mat- ters, and for mindful discussions especially the ones over a glass of sangria. I thank Claudio for teaching me how to interact with the Switzerland, Leonel for various parenting ideas, and Mohammad for proving that a deadline of 15 minutes is not dead enough. I also i thank Andrea for leaving the git server in an adequate state, Pascal for the fresh ideas that he brought to the group, and Oli for shar- ing his DIY experience during coffee breaks. I want to express my gratitude to Haidar for giving me a master class of applying for apartments in Bern, giving away lots of baby stuff, recommending me for a new job, and always sharing new swiss life hacks. I also want to thank David, Kevin, Lars, and Radi for the work that we did together and their technical assistance. I thank Iris for helping me to get an apartment, organizing friendly events, and solving plenty of my problems, many of which I did not even know about. I thank Bettina for taking care of my ever-changing contract extensions and for helping me to organize the defense. My Ph.D. journey did not start in Bern though. I am grateful to Michele Lanza for inviting me to the sunny Lugano and supervising my doctoral research. I will always remember the strict presentation rehearsals, writing of the best abstracts in the world, and Fantozzi quotes during the coffee breaks. I want to thank the whole Lugano team: Andrea for involuntarily appearing in the fun photos that I took (and for guidance in my research), Luca for teaching me Italian and learning Ukrainian from me, Roberto for sharing the sense of beauty in technology, and Tommaso for being a good friend. I want to especially thank all the Italians with whom I worked for inspiring me to improve my culinary skills. Who knows how often I am going to benefit from my Ph.D. diploma, but I can always eat a tasty pasta or a delicious tiramisu. I would not have gone this path if Stephane Ducasse did not invite me to his research group for an internship. I thank him for always staying in touch, working with other Ukrainian students, teaching in Ukrainian universities and regularly brainstorming on the future projects. I also appreciate the help and guidance of Nicolas Anquetil and Anne Etien. I thank the people from Smalltalk and Pharo communities with whom I tightly interacted during the last few years. I am espe- cially grateful to Tudor Girba, Marcus Denker, Esteban Lorenzano, Clement Bera, Alexandre Bergel, Gustavo Santos, Dale Henrichs, Aliaksei Syrel, Max Leske, Guillermo Polito, Stephan Eggermont, Tim McKinnon and others with whom I programmed, brainstormed, or simply went out for a beer. ii I am grateful to the APPS Faculty of the Ukrainian Catholic University for keeping a part my consciousness in my homeland. I thank Yaroslav Prytula for warmly welcoming me every time I visit Lviv, and for the engaging discussions over an aromatic cup of coffee. I thank Oleksii Molchanovskyi for giving me an opportunity to teach in the master program for data scientists and for sharing new ideas about education. I am grateful to Myroslava Romaniuk who doubtlessly programmed day and night to release a new version of Renraku. I thank Oleksandr Zaytsev who appeared out of nowhere, started to build cool projects, and organized a Ukrainian Smalltalk Users Group in Lviv. I am sincerely grateful for all the aid of that my extended family provided over the course of my Ph.D. studies. Some family members understood me, and some did not. Some of them agreed with me, and the others did not. But they believed in me, supported me, and prayed for me. I am especially grateful to my parents who gave me a fantastic start in this life and raised me stubborn enough to survive the Ph.D. experience. Finally, I want to thank my wife who proofread my papers, reviewed my slides, challenged my ideas, prepared tasty lunches, and said “Everything is going to be good” while hugging me at the end of a long day. I thank you, Natalia, for your unconditional love that made me move forward and create without limits. This dissertation could never happen without you. There is one more person. My daughter joined me during my doctoral studies and immediately entered most of the activities of our family. Sophia, I thank you for falling asleep on my chest, stubbornly proposing edits to this dissertation, and teaching me more and more every single day. You are not going to remember the presentations that I rehearsed in front of you when you will learn to speak, and I have removed all the characters that you typed into my manuscripts. Nevertheless, you have changed me, and there is a part of you in this book as well. Yuriy Tymchuk November 21, 2017 iii To Natalia and Sophia who always support my crazy ideas and continue loving me. Наталі та Софії, які завжди підтримують мої шалені ідеї та продовжують мене любити. v A b s t r a c t Programming is a fascinating activity that can yield results capable of changing people lives by automating daily tasks or even com- pletely reimagining how we perform certain activities. Such a great power comes with a handful of challenges, with software main- tainability being one of them. Maintainability cannot be validated by executing the program but has to be assessed by analyzing the codebase. This tedious task can be also automated by the means of software development. Programs called static analyzers can process source code and try to detect suspicious patterns. While these pro- grams were proven to be useful, there is also an evidence that they are not used in practice. In this dissertation we discuss the concept of quality-aware tool- ing — an approach that seeks a promotion of static analysis by seamlessly integrating it into development tools. We describe our experience of applying quality-aware tooling on a core distribution of a development environment. Our main focus is to provide live quality feedback in the code editor, but we also integrate static anal- ysis into other tools based on our code quality model. We analyzed the attitude of the developers towards the integrated static analy- sis and assessed the impact of the integration on the development ecosystem. As a result 90% of software developers find the live feedback useful, quality rules received an overhaul to better match the con- temporary development practices, and some developers even exper- imented with a custom analysis implementations. We discovered that live feedback helped developers to avoid dangerous mistakes, saved time, and taught valuable concepts.
Load more

Recommended publications
  • Making Visual Studio Team System Work in Your Organisation Streamline Your Bug Handling and Development Management System
    Making Visual Studio Team System work in your Organisation Streamline your bug handling and development management system Bikes and Mackas… News Flash Visual Studio Team Edition for Database Professionals •New Visual Studio Database Project – import your database schema and put under source control. – build update scripts or packages and provides a deploy tool to the specified database. • Rename Refactoring • New T-SQL Editor • SchemaCompare • DataCompare • Database Unit Testing – using T-SQL or managed code. • DataGenerator – data based upon your existing production databases – can be deployed to a database prior to running unit tests thus ensuring consistent test results About Adam • Chief Architect for www.ssw.com.au doing: – internal corporate development and – generic off-the-shelf databases – Clients: Royal & SunAlliance, Westbus, Microsoft… • SSW Develops custom solutions for businesses across a range of industries such as Government, banking, insurance and manufacturing since 1990 • President .Net User Group, Sydney • Speaker for Microsoft TechEd and Roadshows, Dev Conn, VSLive…. • Microsoft Regional Director, Australia • [email protected] Agenda 1.History of Bug Systems 2. Exploring VSTS / TFS (a tour) 3. What’s wrong with VSTS for me 4. The Education - What you can customize 5. The Solution - including 3rd Parties How Bug Tracking Systems Work • Everyone needs one – even Microsoft! • Basic Requirements –Searchable – Reportable – Notifications when done •Nice-To-Haves – Source Control Integration – IDE integration (optional)
    [Show full text]
  • A Platform for Software Debugging and Crash Reporting
    Backtrace - A Platform for Software Debugging and Crash Reporting The Backtrace Vision 1 The Backtrace Platform 2 Capture 2 Analyze 3 Resolve 4 Comparing Backtrace with Generic Error Monitoring Tools 5 Backtrace Advantages 6 Feature & Capabilities List 8 The Backtrace Vision Backtrace was founded with a vision to build the best cross-platform, native application crash and error reporting technology for today’s complex software, video game systems, embedded technology, and IoT devices. The software development teams that work in these environments now have a greater impact on how the company performs. When software fails to perform consistently, customers will disappear and employees will function less efficiently. Backtrace developed a platform that empowers organizations to make new and better choices for investing in software. The Backtrace platform has broken new ground with technology that: A. Captures and analyzes crash data from multiple platforms, including desktop (Windows, Mac), mobile (iOS, Android) server systems (Linux), embedded devices (Linux, RTOS), and video game consoles, with new levels of granularity. B. Provides teams with easy to use analytics to prioritize bugs and application failures based on their impact. C. Enables collaboration and integration with the tools you have in place today to speed ability to resolve the issue. Page 1 of 9 Proprietary The Backtrace Platform Backtrace gives your team the automation and diagnostic tools they need to spot errors that matter, understand their impact, explore the context, and zero in on causes in hours or minutes instead of days or weeks. Backtrace is a turn-key solution that was purpose-built for crash and exception analysis.
    [Show full text]
  • Jenkins Job Builder Documentation Release 3.10.0
    Jenkins Job Builder Documentation Release 3.10.0 Jenkins Job Builder Maintainers Aug 23, 2021 Contents 1 README 1 1.1 Developers................................................1 1.2 Writing a patch..............................................2 1.3 Unit Tests.................................................2 1.4 Installing without setup.py........................................2 2 Contents 5 2.1 Quick Start Guide............................................5 2.1.1 Use Case 1: Test a job definition................................5 2.1.2 Use Case 2: Updating Jenkins Jobs...............................5 2.1.3 Use Case 3: Working with JSON job definitions........................6 2.1.4 Use Case 4: Deleting a job...................................6 2.1.5 Use Case 5: Providing plugins info...............................6 2.2 Installation................................................6 2.2.1 Documentation.........................................7 2.2.2 Unit Tests............................................7 2.2.3 Test Coverage..........................................7 2.3 Configuration File............................................7 2.3.1 job_builder section.......................................8 2.3.2 jenkins section.........................................9 2.3.3 hipchat section.........................................9 2.3.4 stash section...........................................9 2.3.5 __future__ section.......................................9 2.4 Running.................................................9 2.4.1 Test Mode...........................................
    [Show full text]
  • Spiraplan External Bug Tracking Integration Guide
    SpiraTest / SpiraTeam / SpiraPlan® | External Bug-Tracking Integration Guide Inflectra Corporation Date: July 8th, 2019 Contents Introduction SpiraTest® provides an integrated, holistic Introduction ........................................... 1 Quality Assurance (QA) management solution that manages requirements, tests and incidents 1. Setting up Data Synchronization ...... 2 in one environment, with complete traceability from inception to completion. 2. Using SpiraTeam with JIRA 5+ ........ 9 SpiraTeam® is an integrated Application 3. Using SpiraTeam with JIRA 3 / 4.... 34 Lifecycle Management (ALM) system that manages your project's requirements, releases, 4. Using SpiraTest with Bugzilla ......... 48 test cases, issues and tasks in one unified environment. SpiraTeam® contains all of the 5. Using SpiraTest with MS-TFS ........ 60 features provided by SpiraTest® - our highly acclaimed quality assurance system and 6. Using SpiraTest with FogBugz ....... 84 SpiraPlan® - our agile-enabled project management solution. 7. Using SpiraTeam with Mantis ......... 96 However, many organizations may be already 8. Using SpiraTeam with ClearQuest 107 using other bug-tracking systems and not want to have to migrate all their users over to 9. Using SpiraTeam with IBM RTC... 119 SpiraTeam. Therefore SpiraPlan, SpiraTest and SpiraTeam are capable of integrating with a 10. Using Spira with Axosoft 14+ ..... 127 variety of commercial and open-source bug- tracking systems. 11. Using SpiraTeam with Redmine . 138 This guide outlines how to integrate and use 12. Using Spira with VersionOne...... 149 SpiraTest, SpiraPlan and SpiraTeam in conjunction with other external Bug/Issue 13. Using Spira with OnTime 11 ....... 159 Tracking systems. 14. Using Spira with GitHub ............. 172 This guide assumes that the reader is familiar with both SpiraTeam and the appropriate tool 15.
    [Show full text]
  • Estudos Preliminares
    IGOR BESSA MENEZE PODER JUDICIÁRIO S JOSE MARIO VIANA JUSTIÇA DO TRABALHO BARBOSA JUNIOR LENIVIA TRIBUNAL REGIONAL DO TRABALHO DA 7ª REGIÃO DE CASTRO E SILVA MENDES FRANCISC O JONATHAN SECRETARIA DE TECNOLOGIA DA INFORMAÇÃO E COMUNICAÇÃO REBOUCAS MAIA Estudos Preliminares Contratação de Suporte Técnico, incluindo atualizações evolutivas e corretivas, para a ferramenta Atlassian Jira e Plugins eazyBI Reports and Charts e Git Integration. Estudos Preliminares - Contratação de Suporte Técnico, incluindo atualizações evolutivas e corretivas, para a ferramenta Atlassian Jira e Plugins eazyBI Reports and Charts e Git Integration. 1 PODER JUDICIÁRIO JUSTIÇA DO TRABALHO TRIBUNAL REGIONAL DO TRABALHO DA 7ª REGIÃO SECRETARIA DE TECNOLOGIA DA INFORMAÇÃO E COMUNICAÇÃO Sumário ANÁLISE DE VIABILIDADE DA CONTRATAÇÃO (Art.14) 4 Contextualização 4 Definição e Especificação dos Requisitos da Demanda (Art. 14, I) 5 Requisitos de Negócio 5 Requisitos Técnicos 6 Requisitos Temporais 6 Soluções Disponíveis no Mercado de TIC (Art. 14, I, a) 7 Contratações Públicas Similares (Art. 14, I, b) 10 Outras Soluções Disponíveis (Art. 14, II, a) 11 Portal do Software Público Brasileiro (Art. 14, II, b) 11 Alternativa no Mercado de TIC (Art. 14, II, c) 12 Modelo Nacional de Interoperabilidade – MNI (Art. 14, II, d) 12 Infraestrutura de Chaves Públicas Brasileira – ICP-Brasil (Art. 14, II, e) 12 Modelo de Requisitos Moreq-Jus (Art. 14, II, f) 12 Análise Comparativa dos Custos das Soluções (Art. 14, III) 12 Escolha e Justificativa da Solução (Art. 14, IV) 15 Descrição da Solução (Art. 14, IV,a) 21 Alinhamento da Solução (Art. 14, IV, b) 22 Benefícios Esperados (Art. 14, IV, c) 22 Relação entre a Demanda Prevista e a Contratada (Art.
    [Show full text]
  • User Documentation for JIRA Software Server 7.1 User Documentation for JIRA Software Server 7.1 2
    User documentation for JIRA Software Server 7.1 User documentation for JIRA Software Server 7.1 2 Contents JIRA Software documentation . 4 Getting started with JIRA Software . 4 Getting started as a JIRA Software manager . 5 Setting up your workspace . 6 Customizing your project . 8 Creating your backlog . 9 Grooming your backlog . 11 Planning your sprint . 13 Tracking your progress . 15 Wrapping up your work . 17 Doing more with your agile projects . 19 Getting started as a JIRA Software user . 22 Learn to plan and estimate for scrum teams . 25 Plan for the team . 26 Customize the team board . 28 Estimate in story points . 29 Analyze team reports . 31 Optimize future plans . 34 Installing JIRA Software . 35 Using JIRA applications with Confluence . 36 Using JIRA applications with HipChat . 39 Using JIRA applications with Portfolio for JIRA . 42 JIRA Software overview . 45 JIRA applications overview . 46 Leading an agile project . 49 Starting a new project . 50 Configuring a project . 51 Creating a board . 52 Configuring a board . 56 Workflows . 81 Organizing work with components . 82 Customizing the issues in a project . 83 Configuring development tools . 84 Configuring collaboration tools . 86 Building a backlog . 87 Using the backlog . 88 Planning a version . 90 Configuring versions in a Scrum project . 91 Configuring versions in a Kanban project . 92 Working with epics . 92 Linking a Confluence page to an epic . 95 Getting to work . 96 Running sprints in a Scrum project . 97 Planning sprints . 97 Monitoring the progress of a sprint . 100 Completing a sprint . 102 Reopening a sprint . 104 Linking a Confluence page to a sprint .
    [Show full text]
  • Sean Tierney - COO of Jumpbox, Inc Goals for This Talk
    Project Management Nirvana with Trac Sean Tierney - COO of JumpBox, Inc Goals for this talk: Understand “WHAT” and “WHY” Ease of deployment with JumpBox Poll: open source dev tools? source control & issue tracking tools? Trac? virtualization (desktop & server)? What makes an effective project management tool? accountability What makes an effective project management tool? scheduling features accountability What makes an effective project management tool? scheduling features accountability What makes an effective project management tool? forecasting scheduling features accountability What makes an effective project management tool? forecasting decision making tool scheduling features accountability What makes an effective project management tool? forecasting passive communication decision making tool scheduling features accountability What makes an effective project management tool? situational awareness forecasting passive communication decision making tool scheduling features accountability efficient knowledge transfer What makes an effective project management tool? situational awareness forecasting passive communication decision making tool scheduling features accountability integration with existing tools efficient knowledge transfer What makes an effective project management tool? situational awareness forecasting passive communication decision making tool scheduling features accountability integration with existing tools efficient knowledge transfer What makes an effective project management tool? situational awareness forecasting passive
    [Show full text]
  • Modern Open Source Java EE-Based Process and Issue Tracker
    MASARYK UNIVERSITY FACULTY}w¡¢£¤¥¦§¨ OF I !"#$%&'()+,-./012345<yA|NFORMATICS Modern open source Java EE-based process and issue tracker DIPLOMA THESIS Monika Gottvaldová Brno, 2014 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Monika Gottvaldová Advisor: doc. RNDr. Tomáš Pitner, Ph.D. ii Acknowledgement I would like to thank Ing. OndˇrejŽižka for his advice and help during the creation of this thesis. iii Abstract This thesis deals with the topic concerning issue tracking systems, their functionality and features. It compares several issue tracking systems, their advantages and disadvantages. It describes a development of such a sys- tem and the use of modern Java EE technologies – JPA, Wicket, and CDI. The main motivation for creating a new issue tracking system and the sub- sequent development is also described. The thesis analyses its basic design and implementation. iv Keywords Issue tracking system, Wicket, modern Java EE, issue, bug, workflow, cus- tomization v Contents 1 Introduction ...............................1 2 Issue Tracking Systems ........................3 2.1 Bugzilla . .4 2.2 Trac . .6 2.3 JIRA . .7 2.4 Mantis . .8 2.5 BugTracker.NET . .9 2.6 Redmine . 10 2.7 FogBugz . 11 3 Analysis of Relevant Processes in Red Hat ............. 14 3.1 RHEL 6 QE . 14 3.1.1 Process Phases Description . 14 3.1.2 Bugzilla Process . 15 3.2 Fedora QE . 16 3.2.1 Process Phases Description .
    [Show full text]
  • JIRA Administration 7.3 Documentation for JIRA Administration 7.3 2
    JIRA administration 7.3 Documentation for JIRA administration 7.3 2 Contents Administering JIRA applications 7.3 . 7 JIRA applications and project types overview . 7 Installing JIRA applications . 10 JIRA applications installation requirements . 10 Installing Java . 12 Supported platforms . 16 End of support announcements . 19 Evaluation installation . 24 Installing JIRA applications on Windows . 25 Uninstalling JIRA applications from Windows . 30 Installing JIRA applications on Windows from Zip File . 31 Installing JIRA applications on Linux . 35 Uninstalling JIRA applications from Linux . 38 Installing JIRA applications on Linux from Archive File . 39 Unattended installation . 45 Installing additional applications and version updates . 46 Connecting JIRA applications to a database . 48 Connecting JIRA applications to PostgreSQL . 48 Connecting JIRA applications to MySQL . 52 Connecting JIRA applications to Oracle . 57 Connecting JIRA applications to SQL Server 2012 . 60 Connecting JIRA applications to SQL Server 2014 . 64 Tuning database connections . 69 Surviving connection closures . 78 Switching databases . 80 Installing JIRA Data Center . 81 Running the setup wizard . 86 Licensing and application access . 89 License compatibility . 90 Extending JIRA applications . 91 Using AppLinks to link to other applications . 92 Administering projects and links across multiple applications . 94 Managing add-ons . 95 Integrating with development tools . 96 Synchronize an account . 101 Configure automatic team invitations . 102 Linking a Bitbucket or GitHub repository with JIRA . 103 Enable Smart Commits . 108 Getting started with Bitbucket and JIRA Cloud . 111 Integrating with other tools . 117 Listeners . 119 Managing webhooks . 121 Services . 121 Integrating with collaboration tools . 123 Upgrading JIRA applications . 127 Upgrading JIRA applications manually . 128 Upgrading JIRA applications with a fallback method .
    [Show full text]
  • User Documentation for JIRA Software Server 7.0 User Documentation for JIRA Software Server 7.0 2
    User documentation for JIRA Software Server 7.0 User documentation for JIRA Software Server 7.0 2 Contents JIRA Software documentation . 4 Getting started with JIRA Software . 4 Getting started as a JIRA Software manager . 5 Setting up your workspace . 6 Customizing your project . 8 Creating your backlog . 9 Grooming your backlog . 11 Planning your sprint . 13 Tracking your progress . 15 Wrapping up your work . 17 Doing more with your agile projects . 19 Getting started as a JIRA Software user . 22 Installing JIRA Software . 25 Using JIRA applications with Confluence . 25 Using JIRA applications with HipChat . 28 Using JIRA applications with Portfolio for JIRA . 31 JIRA Software overview . 34 JIRA applications overview . 35 Leading an agile project . 38 Starting a new project . 39 Configuring a project . 40 Creating a board . 41 Configuring a board . 45 Workflows . 69 Organizing work with components . 70 Customizing the issues in a project . 71 Configuring development tools . 72 Configuring collaboration tools . 74 Building a backlog . 75 Using the backlog . 76 Planning a version . 78 Configuring versions in a Scrum project . 79 Configuring versions in a Kanban project . 80 Working with epics . 80 Linking a Confluence page to an epic . 83 Getting to work . 84 Running sprints in a Scrum project . 85 Planning sprints . 85 Monitoring the progress of a sprint . 88 Completing a sprint . 90 Linking a Confluence page to a sprint . 92 Checking the progress of a version . 93 Using the release page to check the progress of a version . 94 Monitoring work in a Kanban project . 98 Using Active sprints . 100 Releasing a version .
    [Show full text]
  • SENG 371 LAB OUTLINE SOFTWARE EVOLUTION  Bug Tracking System
    3/22/2013 SENG 371 LAB OUTLINE SOFTWARE EVOLUTION Bug Tracking System Types of bug tracking system BUG TRACKING Bug Tracking Tools Bugzilla Prepared by 1 Pratik Jain 2 BUG TRACKING SYSTEM BUG TRACKING Bug Tracking system or issue tracking system or Not only Software Development Team need a bug defect tracking system, is a software application tracking system but sysadmin team, dba team, that keep tracks of reported bugs. network team all require some system to track their work. 3 4 WHY BUG TRACKING TOOLS? BENEFITS Collabortaive Work. Clear centralized overview of development requests(bugs and improvements). Software is a result of many people at different locations different timezones. It helps in next release of Software by using all logs. Communication is crucial, tool makes it easy. Generating reports on productivity of programmers at fixing bugs. Makes easier to track history and evolution of bugs. Improves Communication. 5 6 1 3/22/2013 TYPES OF BUG TRACKING SYSTEM LIFE CYCLE OF BUG Web browser based Client Server based model Distributed Bug Tracking :- Designed to be used with distributed revision control software like Fossil, Veracity and FogBugz. 7 8 MAJOR COMPONENTS BUG REPORT ATTRIBUTES Major Component of Bug tracking system is database that records facts about known bugs. Date : Open Date, Closed Date Status : New, Unconfirmed, Open, Closed, Facts can be :- Deleted, Assigned Request Id: Number Time Severity Detailed Description Identity Severity\Priority : - critical, major, minor\p1,p2 Resolution Category if any, like Gui, Installation or certain module 9 10 BUG REPORT ATTRIBUTES BUG TRACKING SOFTWARES Bugzilla Mantis Jira GNATS Flyspray IBM Rational ClearQuest FogBugz Trac Fossil 11 12 2 3/22/2013 PUBLIC BUG TRACKERS PUBLIC BUG TRACKERS USING BUGZILLA Lots of Open Source projects uses Bug Tracking Open Source Projects:- systems to report a bug.
    [Show full text]
  • Jira Core 7.12 Jira Core 7.12 Documentation 2
    Jira Core 7.12 Jira Core 7.12 Documentation 2 Contents Jira Core Server 7.12 documentation . 4 Jira Core overview . 4 What makes up Jira Core? . 4 See what's possible with Jira Core . 5 Task management . 6 Process management . 8 Project management . 9 Using Jira Core for HR projects . 11 Using Jira Core for Marketing projects . 14 Using Jira Core for Operations projects . 15 Using Jira Core for Finance projects . 16 Using Jira Core for Legal projects . 18 Tips and tricks . 19 How do I build the workflow I want? . 21 Installing Jira Core . 24 Jira applications overview . 25 Permissions overview . 27 Using Jira applications with Confluence . 28 Using Jira applications with Hipchat . 31 Using Jira applications with Portfolio for Jira . 36 Getting started with Jira Core . 39 Getting started as an administrator . 40 Setting up your instance . 40 Creating a project . 42 Adding new users . 43 Managing permissions . 44 Getting started as a project administrator . 46 Customizing your project . 46 Adding users to your project . 47 Getting started as a user . 48 Accessing a project . 48 Creating and working with issues . 49 Searching for issues and filtering . 50 Administering a project . 52 Editing a project's details . 52 Managing project role memberships . 53 Organizing work with versions . 53 Organizing work with components . 55 Workflows . 57 Working in a project . 58 Managing your user profile . 59 Allowing OAuth access . 61 Requesting add-ons . 62 Using keyboard shortcuts . 62 Viewing a project . 64 Viewing a project's components . 64 Viewing a project's issues . 65 Project shortcuts . 65 Working with issues .
    [Show full text]