Bts

Jump to: navigation, search

Introduction

Our Bug Tracking System tool is Mantis.

Before editing any information, authentification will be needed from you.

When you open an account, an email will be sent to you. In the event that you do not receive any email, please check that the latter has not been diverted to another folder or deleted by the anti-spam tool of your email program.

Report a bug in Mantis (for Testers and Reporters)

Before reporting a bug, take your time to perform the following tasks :

  • Check that the bug has not already been reported.
  • Right at the start, check the items to avoid that they are sent to the wrong category.
  • Choose the right category :
Heading Particulars
Admin Relates to configuration/administration section
Booking Relates to reservations bookings
Flights Management Relates to the flights schedule
Accounting Management Relates to account & finance
Documentation Relates to information/documentation
Update Relates to the update tool
Translation Relates to translations (Phrase in the wrong language or missing phrase)
  • Choose the right version of OpenFlyers on which you have detected the bug (Actually we use filters and it may happen that we have missed a bug that has been tagged under a wrong version)
    • 1.3.x
    • 2.0alpha
    • 2.0
  • Summary :
 Write down a clear description that will include,if possible, the reference number of the corresponding scenario (cf. script)
  • In the description

If the bug is an online version, indicate the origin of your test. If it is an offline version, give as much information on your database situation and eventually save your document to have a clear picture of the bug in its reproductive state

The description needs to be as complete as possible for the developers to identify the site of the problem.

  • The real nature of the problem and its manifestation (failure to display, warning, etc)
  • Communicate all the symptoms to understand the WHYs of the problem, namely :
    • The OS used (Windows 98, Windows XP, Linux, UNIX, Jaguar, etc.)
    • The Browser used (Safari, Internet Explorer, Netscape Navigator, Firefox, etc.)
    • The Browser´s version.
  • Thank you for communicating to us the following if you are using an OpenFlyers version that is not hosted by the OpenFlyers Association (Note that if the version you are using is hosted by our Association, the internet address will be in the following form : nameoftheclub.openflyers.org):
    • phpinfo() might be useful to detect a likely configuration problem with your server
    • To save time, we would appreciate if you could check if all files have been uploaded correctly before reporting a bug (presence on the server, all modification brought under control).

Please note that we do not solicit Free Hosting Services.In fact the latter are quite limited when compared to Paying Hosting Services. Our programme works best when used on a standard Linux server (with possible minor variables) but with options that can sometimes only exist on Paying Hosting Services. The 2.0 version might, for example, be more demanding than version 1.2 as far as prerequisites are concerned.

  • A screen copy is sometimes worth more than a thousand words. Please do not abuse, we are only looking for solutions to fix the bug not to avoid it.
  • While the bug is being fixed, use the notes for additional info to avoid email duplication.

If the bug is an online version, indicate the origin of your test. If it is an offline version, give as much information on your database situation and eventually save your document to have a clear picture of the bug in its reproductive state

  • When the bug has been fixed, you will receive an email. You will then need to remove the bug. If you have noted that the solution does not correspond to your description ( partially or totally ), please do not hesitate to restart again. If by the way, you detect a new problem, please react promptly by sending a fresh description of the bug presence. The removal of the bug needs to be carried out at source.
  • Failure to take appropriate actions within reasonable time will entail our developer to remove the bug himself.

Description of the situation and the fixing in progress

Situation

Heading Description By whom
new New bug, first state The bug initiator
feedback Needs more information. the bug initiator should be on the alert The administrator or developer
acknowledged The bug has been read but is not confirmed nor assigned The administrator or developer on whom the bug depends
confirmed The bug is confirmed and can be reproduced The administrator or developer
assigned The bug is assigned to a developer The administrator takes care of the bug
resolved The bug should by now be fixed, waiting for confirmation of its fixing by the initiator of the bug The developer who has fixed the bug
closed The bug is closed The initiator of the bug or the administrator who has confirmed the bug

Fixing

Name Description
open Open bug on waiting
fixed Bug already fixed and confirmed by the developer in charge
reopen Bug still existing after correction
unable to reproduce The bug that has been reported cannot be reproduced
not fixable No possibility of correcting the bug
duplicate The bug has already been modified in Mantis
no change required Is not considered a bug
suspended The bug is put aside
won't fixed The bug is detected but will not be fixed

Fixing of bugs in Mantis (for developers and administrators)

  • When a bug is already being fixed, caution should be taken to name it as such in the version that is already being modified (namely the future published version)
  • The removal of a bug needs to be carried out at source.
  • If appropriate action is not taken in due time to remove the bug, the developer will remove it himself.

Always keep an eye on your bugs

Compliance with Web Standards

We are commited to comply strictly to web standards namely the Xhtml 1.0 standard

There are several tools to verify the validity of a page.

How to use the W3C tool W3C ? :

  • Display your page by using an an internet browser (firefox or internet explorer)
  • Save the page separately on your hard disk
  • Go to W3C validating page validator
  • Upload the saved file on the hard disk
  • See the result