Quality Assurance Module
The Quality Assurance module, or QA for short, is designed to ensure that all database and application objects are suitable for production environments based on sets of checklists. In the QA module you will find three forms:
The overview form is the main form in the QA module. This is where you track your QA. The navigation grid shows four fields: Checklist Name, QA Object, QA Required and Open Findings. Checklist Name is picked up from the Checklists. On the “Log Findings” tab you have two grids where the first one is where you document when the QA was performed including your comments. The second grid shows your findings. Here you report all your findings on all objects.
As an example, I’ve added a finding on the table “stbl_Database_R3Upgrader_BuildScripts” that it should be deleted. When this is done I will set the status of this finding to “Closed” and the object will no longer have any open findings.
Every time you make a new version of an object, the “QA Required” field will be set to checked. When you add a comment in the Log-grid, this field will be set to unchecked. The other tab in the overview form is “Checklist”. This shows the checklist items related to this object.
Checklists
Here you register which checklist items you want on each object type. R3CurrentBuild comes with a standard set of checklist items, but if you want to add custom items which apply in your environment, this is where to do it. In R3CurrentBuild we have the following lists: CR3 Reports, SPs and Functions, Tables, Views, Web Client Projects, Win Client Projects. Example of checklist items are “Is this SQL object in use?”, “Permissions to groups granted” and “Tab order is correct”.
Excluded Objects
In this form you register all the objects that you do not want the QA module to handle, for example old modules, import tables or similar.
Version Tracking
The Version Tracking module is tightly connected to the QA module, although you don’t need to use both. This module keeps track of what’s changed since last release. This is great to use if you have modules in your system that you release to others, for example when the technology department releases new builds. In this module there are two forms:
Modules
In this form you register the modules you want to keep track of. You set up each module with a database namespace, Win Client namespace, Web Client namespace, Report namespace, owner and responsible. The responsible person will automatically be assigned any QA requirements in the QA Overview form.
Change Log
This is the main form for the Version Tracking module. In the navigation grid you have three fields; Module, Version and Release. When you click the “New unreleased Version” this will add a new version for each module. Then you can set the “Planned Release” field for each module. When you are releasing the version, add your comments to the “Overall Comments” tab and click the “Find Changes” button to populate DB Changes, Win Client Changes and Report Changes. Then click the “Set As Released” button
