Edinburgh Core Database Group

Capel Group

Cohn Group

Gaido Group

Jain Group

Keast Group

Lessard Group

Little Group

McMahon Group

Mendelsohn Group

Potter Group

Southard-Smith Group

Vezina Group

Editorial Office Protocols

Testing

Software Testing is aimed at evaluating the capability and the quality of the system under test, with respect to the context in which it is intended to operate.
Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding as many errors in the software as possible.
Software Testing can also be stated as the process of validating and verifying that a software program/application:

  1. meets the business and technical requirements that guided its design and development;
  2. works as expected.

For the GUDMAP project, all defects/concerning issues are reported in Mantis, basically a bugtracking system but which can also be used to track other issues like new requirements from the editors. Its clean interface and numerous features make bug/issue tracking fast and easy and it can also notify developers and normal users of reported bugs through email, RSS feeds, and even Twitter.

 

Bug Fixing

Once a defect has been reported in Mantis, there are some basic steps to follow before bug fixing takes place.

 

After the software deployment has been made, it is the tester’s job to verify the resolved issues and see if the reported bugs have been fixed.
If the tester feels that a bug no longer exists in the software, he/she can change the status of that bug to “CLOSED”. This state means that the bug is fixed, tested and approved. However, if the bug still exists even after it has been resolved by the developer, the tester can reopen the issue and change the status to “NEW”.