SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Bug Tracking System Vs SVN/CVS

paul avatar
paul
8 diapositives · 895 Views · Oct 18, 2011

Bug Tracking System Vs SVN/CVS. Presented by Sneha Mudumba. Bug tracking system.

Bug Tracking System Vs SVN/CVS - slide 1
01 / 8Bug Tracking System Vs SVN/CVS
1 / 17

Télécharger la présentation

Bug Tracking System Vs SVN/CVS
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Bug Tracking System Vs SVN/CVS Presented by Sneha Mudumba

  2. Bug tracking system • It is a software application that is designed for quality assurance and helps the programmers to keep track of reported software bugs in their work. It is a sort of issue tracking system. • The major component of bug tracking system is a database that records facts about known bugs.

  3. It is an open source version control system that keeps track of all changes in a set of files, typically the implementation of a software project and it allows several developers to collaborate. The major components in CVS is a repository which is master copy where CVS stores a full revision history. Concurrent version system

  4. Features of bug tracking system • The major component of bug tracking system is a database that records facts about known bugs.Facts may be the time of the bug, the nature of the bug, the behavior and details on what produced a bug. • Typical bug tracking system supports the concept of lifecycle for a bug which is tracked through status assigned to the bug.

  5. Features of CVS. • The key terms of CVS are: Repository:The master copy where CVs stores the revision History. Working Copy:The copy in which actual changes are made. Typical CVS system supports several programmers to work concurrently.The server will accept the changes made to the most recent version of file.Developers are therefore expected to keep their working copy up to date by incorporating other peoples changes.

  6. Limitations of CVS1. CVS only shows what the conflicts are but does not give a procedure to solve it 2. Limited support for Unicode text file and non -ASCII filenames. • Examples: Mantis and TRAC:Mantis is an example of web based bug tracking system.It is written in PHP and requires a SQL database Server.It is a lightweight ,simple bug tracking system. TRAC matches to mantis.

  7. Conclusion So the Bug tracking system and the Concurrent version system both enable the programmers to keep track of the bugs by using different mechanisms and there by enable the programmers to resolve the errors in a easy way