Week Assignment Source Code Control (SCC) & Bug Tracking Systems Hans-Petter Halvorsen

Size: px

Start display at page:

Download "Week Assignment Source Code Control (SCC) & Bug Tracking Systems Hans-Petter Halvorsen"

Justin Sanders
5 years ago
Views:

1 Week Assignment Source Code Control (SCC) & Bug Tracking Systems Hans-Petter Halvorsen

Implementing your System with focus on Source Code Control Try to use some of the more advanced Source Code Features in

2 1. SCC Systems Overview Everybody should collaborate creating a document giving an overview of different SCC systems today. 2. Bug Tracking & Reporting in Visual Studio Team Services (VSTS) -> Work Items - Bug 3. Cont. Implementing your System with focus on Source Code Control Try to use some of the more advanced Source Code Features in VSTS See Next Slides for more details... Note! All Documents, Code, etc. you create should be uploaded to Visual Studio Team Services (VSTS) Week Assignment

3 Introduction Source Code Control (SCC) & Bug Tracking Systems Hans-Petter Halvorsen

4 Software Configuration Management (SCM) Software Configuration Management is the process of managing all the pieces and parts of artifacts produced as part of software development and support activities. We will focus on Tools that need to be brought in to facilitate the management of these artifacts Visual Studio Team Systems is such a Tool Tools for handling the Source Code Source Code Control (SCC) Software Configuration Management is much more than just creating and keeping multiple versions of code or documents

5 SCM Artifacts Examples Requirements Specifications Design Specifications Source Code Control Programming Code, e.g., C# Code Database Tables (Diagrams and SQL) and Initialization Data (SQL), e.g., Post Numbers,... Executable Code, Builds Test Cases Bugs (Bug Tracking) Support Incidents

Software Builds, Deployment, Continuous Integr

6 Tools for Configuration Management These configuration management tools may be viewed in three tiers: 1. Source Code Control (SCC) Tools, e.g., Git, TFS, SVN, CVS 2. Software Builds, Deployment, Continuous Integration (CI), e.g., Jenkins These tools make sure the software is always ready to be tested based on the updated Code base 3. Development (Bug Tracking or Issue Tracking) and Support Process Activities Visual Studio Team Services has all these 3 tiers

7 Jenkins Jenkins is a selfcontained, open source automation server which can be used to automate all sorts of tasks related to building, testing, and delivering or deploying software.

8 SCC Source Code Control Systems Hans-Petter Halvorsen

9 SCC Systems Concurrent Versioning System SVN

10 Cloud-based SCC Hosting Services Visual Studio Team Services ( TFVC or Git GitHub ( GitLab ( Bitbucket ( Mercurial or Git

11 Source Code Control SCC Repositories Cloud-based SCC Hosting Services (Monthly payment/5 users free of charge/free for open source projects) Git TFVC or Git Git or Mercurial

12 Centralized/Client Server Architecture Client Client Client Network Client Server Repository Repository: Source Code Database

13 Distributed Version Control Systems Repository peer-to-peer peer-to-peer Repository Repository Repository: Source Code Database Repository

14 Bug Tracking Systems Hans-Petter Halvorsen, M.Sc.

15 Bug Tracking Systems A bug tracking system or defect tracking system is a software application that keeps track of reported software bugs in software development projects. It may be regarded as a type of issue tracking system. Typically bug tracking systems are integrated with other software project management applications e.g., Visual studio Team Services, Jira, Bugzilla, etc.

16 Bug Tracking Systems Tissue Bugzilla

17 Bug Reporting and Tracking Example Developer Fix Bugs Check if Bug Fixes are Approved Tester Bug Tracking System Report Bugs Check if Bugs are Fixed Assign Responsible Test Manager, Person Project Manager, QA Department Go through Lists of Not Fixed Bugs, Fixed Bugs, etc.

18 Title Assign To (who shall fix the Bug) In which Module was the Bug found? When (in which Iteration) was the Bug found? You can also upload Screen shots! Important information! Important to Help the Developer to find the Bug Bug Reporting and Tracking in VSTS

Source Code Control Systems The Class should collaborate creating a common document that gives an overview of SCC systems today Everybody should work with and update the

20 Source Code Control Systems The Class should collaborate creating a common document that gives an overview of SCC systems today Everybody should work with and update the document at the same time We will use Google Docs for Real-Time Collaboration Individual: Each Student should get overview of at least one SCC System See Next Slides for more details...

21 Concurrent Versioning System SVN

23 Bug Tracking and Reporting with Visual Studio Team Services (VSTS) Source Code: Make sure all your code is checked in into VSTS before you start Perform Code Review/Testing of the Application/Module to another Developer in the Team Work Items: Report Bugs, New Features, etc. as Work Items in VSTS Create Queries: Make different Queries. Go through the Work Items in VSTS with the Developer. Prioritize them See Next Slides for more details...

24 Work Items and Queries Work Item - Bug/New Feature Each member in the Group should report 2-5+ Bugs/Feature Request in VSTS based on the Code Reviews Queries Each member should create at least 1 Personal Query (My Queries) and 1 Team Query (Shared Queries)

25 Title Assign To (who shall fix the Bug) In which Module was the Bug found? When (in which Iteration) was the Bug found? You can also upload Screen shots! Important to Help the Developer to find the Bug Important information!

are Approved Tester VSTS Report Bugs Check if Bugs are Fixed Assign

26 Make Queries that can handle these situations! Bug Reporting and Tracking Example Developer Fix Bugs Check if Bug Fixes are Approved Tester VSTS Report Bugs Check if Bugs are Fixed Assign Responsible Test Manager Person or Project Manager Go through Lists of Not Fixed Bugs, Fixed Bugs, etc.

Bugs A software bug is an error, flaw, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended

27 Bugs A software bug is an error, flaw, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways They found a bug (actually a moth) inside a computer in 1947 that made the program not behaving as expected. This was the first real bug. Debugging: Find and Remove/Fix Bugs

28 Bugs vs. Features It's not a bug - it's an undocumented feature J For as long as I've been a software developer and used bug tracking systems, we have struggled with the same fundamental problem in every single project we've worked on: how do you tell bugs from feature requests?

29 Work Items New Bug Test your Application/System. Report Bugs in TFS/VSTS

30 Queries Used to find existing Work Items You may create different Queries to make it easy to find the Work Items you need Queries may be personal or visible for everybody in the project (Team Queries) Make one or more Queries in order to find your Bugs (Bugs reported on you) 35

31 Creating a Query - Example

32 [Any] Query Variables

Hans-Petter Halvorsen University of Southeast Norway www.usn.

33 Hans-Petter Halvorsen University of Southeast Norway Web:

Week Assignment. Source Code Control (SCC) & Bug Tracking Systems. Hans-Petter Halvorsen

Week Assignment. Source Code Control (SCC) & Bug Tracking Systems. Hans-Petter Halvorsen 2017.03.06 Week Assignment Source Code Control (SCC) & Bug Tracking Systems B. Lund. Lunch. Available: http://www.lunchstriper.no, http://www.dagbladet.no/tegneserie/lunch/ Hans-Petter Halvorsen Note!