This table stores "action" tests steps, i.e. steps with an action and expected result, which were formerly stored in TEST_STEP
The step's action
clé étrangère vers un ATTACHMENT_LIST, l'entité qui gère les pièces jointes.
The step's expected result
Shared key with TEST_STEP table
Add action word table
Date of last implementation
Technology used for last implementation
Create ACTION_WORD_FRAGMENT table
primary key, auto-generated
Foreign key to the action word
the fragment order in action word fragment list
Create action word library table
Foreign key to ATTACHMENT_LIST
The auto-generated id
Create action word library node table
Foreign key to the ACTION_WORD_LIBRARY
The auto-generated id
Create new table for Action word parameter elements
Shared key with ACTION_WORD_FRAGMENT table
the default value of the action word parameter
the name of the action word parameter
Create new table for Action word parameter value
the action word parameter by which this value replaces
primary key, auto-generated
the keyword test step in which this value is used
the value of the action word parameter value
Create new table for Action word text elements
Shared key with ACTION_WORD_FRAGMENT table
the content of the action word text
Cette table stockera les pieces jointes. La piece elle même est un blob stocke a part dans la table ATTACHMENT_CONTENT. La relation entre les deux tables est 1-1
Date de l'ajout de la piece jointe.
clé primaire de la piece jointe. Devrait être autogénérée.
cle etrangere vers la table ATTACHMENT_CONTENT
nom de la piece jointe
taille de la piece jointe en octet. Cette information est déterminée au moment de l'upload et doit etre fournie a la base dès sa création
type de la piece jointe. Cette information pourrait etre trivialement deduite du nom de fichier
Cette table contient le contenu d'une pièce jointe, dont les meta infos sont stockees dans la table ATTACHMENT. La relation entre les deux tables est 1-1
clé primaire du contenu de la piece jointe. Devrait être autogénérée.
Le contenu de la piece jointe.
Cette table contient le contenu d'une pièce jointe, dont les meta infos sont stockees dans la table ATTACHMENT. La relation entre les deux tables est 1-1
clé primaire du contenu de la piece jointe. Devrait être autogénérée.
Le contenu de la piece jointe.
Cette table matérialise une liste d'ATTACHMENT. Bien qu'elle ne contienne que sa clé primaire, sa raison d'exister est, au niveau de l'application, de fournir une entité indépendante des entités métier auquel on rajoute les pièces jointes.
clé primaire, devrait être autogénérée.
Table for the automated executions extender. An automated execution is an extension to Executions that handles things related to test automation. The correct business model would have been that an automated execution is a specialization of execution, thus inherited from it. Sadly Hibernates got in the way so we came up with that solution instead.
order of automated executions extenders within an automated suite
foreign key to the Execution it attaches to.
Name of the node which ran the test
a short debriefing of a test once it has been executed, for instance an error message
urls longer than 300 chars should go to hell
foreignkey of the suite this execution belongs to
we save that information as soon as the auto execution is created, because it may change in the future (even if the test case that this execution is linked to stays otherwhise the same)
Creation of the automated suites table. Note that althought its ID is still the primary key, it won't be autogenerated : the system will supply it along the rest instead. A automated suite groups together a bunch of test automation executions, which themselves refer to test automation tests.
foreign key to ATTACHMENT_LIST, entity dealing with attachment.
Creation of the table AUTOMATED_TEST
create automated test technology table
Create table AUTOMATION_REQUEST to Gherkin's test cases
fk to the host project
Creating the AutomationRequestLibrary
autoincremented primary key
fk to the attachment list
The automation request library content table
Foreign key to the content
Foreign key to the library
Create action word library node relationship table
Foreign key to parent node
Order in its parent node
Foreign key to child node
closure table for action word library nodes. Its content is set and modified by 4 triggers
cle etrangere vers le noeud parent. La relation est parfois d'un noeud vers lui meme.
stores how deep is the descendant element nested in the subtree of the ancestor element
cle etrangere vers l'element fils. La relation est parfois d'un noeud vers lui meme.
To connect Squash TM to a bugtracker, you must provide the name and the url of the bugtracker. The mantis plugin is shipped with the application IFRAME_FRIENDLY :tells if the bugtracker page can be accessed through an iframe : if the response header of the bugtracker page has the property [X-Frame-Options = DENY] the answer is false URL : must point to the base name of the end point. Eg : http://www.yourdomain.com/mantis . Tips : Prefer IPs over localhost and domain names over IPs. If you don't some minor issues may occur when reporting an issue.
primary key, should be auto-generated.
tells if the bugtracker page can be accessed through an iframe
tells what kind of connector should be used
Bugtracker project represent the project's name in a configured bugtracker
This table stores "call" tests steps, i.e. steps which call an entire test case
A reference to the called dataset (if any). The fk constraint must set null when the dataset is deleted.
ID of called test case
Says whether the parameters of the called test case must be set by the caller test case or not
Shared key with TEST_STEP table
Cette table gere les campagnes proprement dites. Une entree dans cette table indique que l'element reference dans la table CAMPAIGN_LIBRARY_NODE par la cle primaire (egalement cle etrangere) est de type campagne.
Drapeau indiquant si l'utilisateur a choisit une determination automatique de la date de depart effective ou non.
Date de fin effective (reelle) de la campagne.
Drapeau indiquant si l'utilisateur a choisit une determination automatique de la date de fin effective ou non.
Date de depar effective (reelle) de la campagne.
a reference lavel for a campaign
Date planifiee de fin de la campagne.
Date planifiee de debut de la campagne.
Cette table est rudimentaire. La cle primaire est simplement une cle etrangere vers la table CAMPAIGN_LIBRARY_NODE (relation qualifiante). Une entree dans cette table indique que l'element indexe par cette cle est de type repertoire.
cle primaire, qui est une cle etrangere vers la table CAMPAIGN_LIBRARY_NODE. Ne doit donc pas etre autogeneree.
Cette table gere les bibliotheques de campagnes. Une bibliotheque de campagnes peut contenir plusieurs repertoires et/ou campagnes, ces deux entites etant regroupees sous l'appellation generique d'element de bibliotheque de campagnes (campaign library nodes).
clé étrangère vers un ATTACHMENT_LIST, l'entité qui gère les pièces jointes.
cle primaire autogeneree
Cette table gere les bibliotheques de campagnes. Une bibliotheque de campagnes peut contenir plusieurs repertoires et/ou campagnes, ces deux entites etant regroupees sous l'appellation generique d'element de bibliotheque de campagnes (campaign library nodes).
cle etrangere vers un noeud de la bibliotheque de campagnes.
cle etrangere vers une bibliotheque de campagnes.
Cette table represente un element (generique) faisant partie d'une bibliotheque de campagne. Cet element generique peut representer soit un repertoire, soit une campagne. Pour cette raison, que l'utilisateur cree l'un ou l'autre cette table sera necessairement alimentee, et contiendra la cle primaire de l'element en question. Toutefois le type reel de l'element (campagne ou repertoire) n'est pas renseigne, il est necessaire de rechercher si la cle est referencee dans la table CAMPAIGN_FOLDER ou CAMPAIGN pour determiner si cet element releve de l'un ou l'autre.
clé étrangère vers un ATTACHMENT_LIST, l'entité qui gère les pièces jointes.
cle primaire autogeneree
nom du createur de cette campagne.
Date de creation de cette campagne. Il s'agit de la date de creation de l'entree dans la base, non d'une date metier.
Une description associee a cet element. Devrait etre un champ texte long ou un clob.
Nom du dernier utilisateur ayant mis a jour cet instance.
Date de derniere mise a jour de cette instance.
Le nom/label de l'element en question.
FK to the Project to which belongs this resource
We have to set campaign_ID and Test_plan_order to "true" to let hibernate persist new items
cle etrangere vers CAMPAIGN
clé primaire du test plan. Devrait être autogénérée.
the dataset the test plan item should use so that new iterations will now use those datasets
cle etrangere vers TEST_CASE
numéro d'ordre d'une execution dans la liste des test plans d'une itération.
Id de l'utilisateur assigné a ce cas de test reférenncé
This table holds which CHART_COLUMN_PROTOTYPE are the axes for a given chart.
may define an additional operation about how data are grouped on this axis, most of the time 'NONE' is fine, however for Timestamp columns an adequate aggregation (day, month etc) may be useful
in which order the axis are processed (if relevant)
foreign key to CHART_COLUMN_PROTOTYPE
foreign key to the chart_definition
a column to persist cuf id relative to this axis
a label for this axis. If non null, will override the default label in the CHART_COLUMN_PROTOTYPE
This table holds referential data only (users cannot populate it) : it lists every single columns that can be used in a custom chart. Here, a column is basically an attribute from an entity. Theses columns are merely options proposed to the user. Once the user confirmed that he wants to include a particular column in a custom chart, and in which context (as a measure, an axis or applying a filter on it), the entries from this table will be referenced by entries in tables FILTER, AXIS_COLUMN or MEASURE_COLUMN. Some columns aren't proper attributes of an entity but rather the result of an expression. This expression is itself expressed as a CHART_QUERY. For this reason a COLUMN_PROTOTYPE may point to a CHART_QUERY via a (nullable) foreign key. Last, some columns aren't supposed to be available to the user and used in a chart. The attribute 'BUSINESS' = true indicates that the user is allowed to use them.
The name of the attribute of the entity
complementary information about the nature of this column : native attribute ('ATTRIBUTE'), computed field ('CALCULATED') - often as a subquery -, or custom field ('CUF')
tells whether this column is public or internal.
the column ID
complementary information about the nature of this column : native attribute ('ATTRIBUTE'), computed field ('CALCULATED') - often as a subquery -, or custom field ('CUF')
Data type of the attribute
a complementary qualifier for ENTITY_TYPE, used when an entity has an auxialiary role regarding another entity. For instance an InfoListItem may have a role of nature for a TestCase, or category for a RequirementVersion. May be null if nothing special about it.
The kind of entities this column belongs to
The default label for this column.
optional foreign key to a (sub) CHART_QUERY
The CHART_COLUMN_ROLES precises in which roles a particular CHART_COLUMN_PROTOTYPE can be used : 'AXIS', 'FILTER' or 'MEASURE'.
foreign key to CHART_COLUMN_PROTOTYPE
name of a role for the referenced column
The table CHART_DEFINITION describes the custom charts created by the user. Along with the informations stored in this table a CHART_DEFINITION refers to a CHART_QUERY, which aggregates the unit blocks that constitute the data elligible for plotting.
autogenerated ID
whether this chart is a 'PIE', 'BAR' etc
additional informations about this chart
The name of this chart
cle etrangere vers le projet.
a column to persist the scope type
whether this chart is 'PRIVATE' or 'PUBLIC'
A CHART_FILTER restricts the values a CHART_COLUMN_PROTOTYPE may have for a given chart. A CHART_FILTER will compare the value of a CHART_COLUMN_PROTOTYPE with one or several CHART_FILTER_VALUES using a comparison operator.
foreign key to a CHART_COLUMN_PROTOTYPE
foreign key to the chart_definition
a column to persist cuf id relative to this filter
autogenerated ID
a comparison operator
This table holds the values used in a CHART_FILTER.
foreign key to CHART_FILTER
a value for this filter
This table store which columns are the measures the user is interested to see. They consists of an aggregation operation applied to a CHART_COLUMN_PROTOTYPE.
foreign key to the CHART_COLUMN_PROTOTYPE this measure applies to
foreign key to the chart_definition
a column to persist cuf id relative to this measure
a label for this measure. Will override the default label of the column prototype if non null.
the measure applied to the column
the order in which the measure will be displayed when the chart is rendered.
The table CHART_QUERY aggregates 1..* CHART_MEASURE_COLUMN, 1..* CHART_AXIS_COLUMN and 0..* CHART_FILTER (see these table for more informations). It may be referenced by either a CHART_DEFINITION (as a query), either a COLUMN_PROTOTYPE (as a subquery).
autogenerated ID
generally indicate whether should use inner join or left join when a natural join is possible. Possible values : INNER_JOIN or LEFT_JOIN
internal usage, when this CHART_QUERY is a CHART_COLUMN_PROTOTYPE subquery the name helps identify which one
says how the query builder should integrate this query to a main query. Accepts values : MAIN, SUBQUERY or INLINED
The scope is a particular filter on the data : it restrict the perimeter from which the measured entities can be chosen, for example from project X and folder Y
foreign key to a CHART_DEFINITION
the id of the referenced entity
the type of the referenced entity
Cette table gere la hierarchie entre elements d'une bibliotheque de campagne, associant un element fils a un repertoire parent (si non NULL) ou eventuellement aucun (NULL, dans le cas ou l'element est a la racine de la bibliotheque de campagne).
cle etrangere vers le repertoire parent (il s'agit necessairement d'un repertoire).
cle etrangere vers l'element fils.
closure table for campaign library nodes. Its content is set and modified by four triggers, see changeset 'tm-1.3-feat-1112.07-mysql' or 'tm-1.3-feat-1112.07-h2'.
cle etrangere vers le noeud parent. La relation est parfois d'un noeud vers lui meme.
stores how deep is the descendant element nested in the subtree of the ancestor element
cle etrangere vers l'element fils. La relation est parfois d'un noeud vers lui meme.
Create Connection Attempt Log Table
autogenerated ID
Date of connection
login used to connect
if connection succeeded or not
Create tables CORE_PARTY, CORE_TEAM
The table CORE_PARY_AUTHORITY stores personal authorities. As for TM 1.8.0 the users and teams now have blanket permissions (aka authorities) for themselves, not only via core_group membership. However, a user will still belong to one of the CORE_GROUPs and the personal authorities will stack with the authorities of the group they belong to.
The authority
The CORE_PARTY
Create tables CORE_PARTY, CORE_TEAM
Date de creation. Il s'agit de la date de creation de l'entree dans la base, non d'une date metier.
Nom du dernier utilisateur ayant mis a jour cet instance.
Date de derniere mise a jour de cette instance.
cle primaire, qui est aussi une cle etrangere vers la table PARTY_ID Ne doit donc pas etre autogeneree.
create table team member
This table contains the relations between two custom reports nodes. If a node is root, parent id will be null and descendant id will be itself. a given node can be referenced as descendant only one time so we can map the join with hibernate
cle etrangere vers le noeud parent
numéro d'ordre du noeud dans son parent
cle etrangere vers l'element fils.
closure table for custom report library nodes. Its content is set and modified by four triggers
cle etrangere vers le noeud parent. La relation est parfois d'un noeud vers lui meme.
stores how deep is the descendant element nested in the subtree of the ancestor element
cle etrangere vers l'element fils. La relation est parfois d'un noeud vers lui meme.
Create new tables to store the scope and the columns of a custom export
Foreign key to the Custom Export
Create new tables to store the scope and the columns of a custom export
Foreign key to the Custom Export
Creates a table for Custom Fields
CF : simple, SSF : multiple-choice
this column is used by rich text cufs. It contains HTML data.
a column to persist numeric cuf
Creates a table for Custom Fields Binding
Creates a table for Custom Fields Options
Creates a table for rendering locations of a bound custom field
The table CUSTOM_FIELD_VALUE holds instances of a CUSTOM_FIELD that are bound to instances of : test cases, requirement version, campagnes, iterations and test suites. A custom field value is created when a custom field binding is created or an entity subject to an existing custom field binding is created. A custom field value is destroyed when the bound entity instance is destroyed or the custom field binding is destroyed. Note that in this table the coupling between the custom field value and the bound entity is week : it consists of a pair of Type/ID (BINDABLE_ENTITY_TYPE and BINDABLE_ENTITY_ID) rather than a foreign key to the said entity, nor is true the opposite ( ie no FK from a test case to a custom field value).
the id of the bound entity
the kind of entity. Note that this information is also contained by the custom field binding.
dernomalize the custom field id for custom report queries
the custom field binding that holds all the data
technical id
CF : simple, RTF : rich text field
this column is used by rich text cufs. It contains HTML data.
a column to persist numeric cuf
the value of that particular custom field value
Creating the values table for multi-valued custom fields, much like CUSTOM_FIELD_OPTION is. Note : the DELETE CASCADE on the foreign key is necessary because Hibernate won't do it (as specified, see HHH-5529)
This table contains the relations between two custom reports nodes. If a node is root, parent id will be null and descendant id will be itself. a given node can be referenced as descendant only one time so we can map the join with hibernate
cle etrangere vers le chart.
pk genere
cle etrangere vers le dashboard.
Create new object CustomExport in Custom Report Workspace
The auto-generated id
The name of the Custom Export
Foreign key to the Project
This table contains the relations between two custom reports nodes. If a node is root, parent id will be null and descendant id will be itself. a given node can be referenced as descendant only one time so we can map the join with hibernate
pk genere
cle etrangere vers le projet.
This table contains the relations between two custom reports nodes. If a node is root, parent id will be null and descendant id will be itself. a given node can be referenced as descendant only one time so we can map the join with hibernate
pk genere
cle etrangere vers le projet.
FK to ATTACHMENT_LIST
pk genere
fk to the containing CUSTOM_REPORT_LIBRARY
pk genere
cle etrangere vers le dashboard.
pk genere
cle etrangere vers le report.
Add tables to handle test cases DATASETS
the DATASET primary key
the dataset name, should be unique among parameters of the same test case
the test case where the parameter is declared
Add tables to handle test cases DATASETS
the dataset holding the value for the parameter
the DATASET_PARAM_VALUE primary key
the parameter to set the value of
the value for the parameter in the dataset
Adding denormalized field option table for editable denormalized list valued cufs
Create table for denormalized field rendering location
The table DENORMALIZED_FIELD_VALUE holds instances of a FIELD that are bound to instances of : executions, execution-steps when they are created from test-cases or test-case-steps holding CUSTOM_FIELDS. A "denormalized field value" is destroyed when the "denormalized field holder" instance is destroyed. Note that in this table the coupling between the "denormalized field value" and the "denormalized field holder" is week : it consists of a pair of Type/ID (DENORMALIZED_FIELD_HOLDER_TYPE and DENORMALIZED_FIELD_HOLDER_ID) rather than a foreign key to the said entity, nor is true the opposite ( ie no FK from an execution to a denormalized field value).
the custom field value where the denormalized field is copied from
the id of the denormalized field holder.
the kind of entity.
CF : simple, SSF : multiple-choice
this column is used by rich text cufs. It contains HTML data.
a column to persist denormalized numeric cuf
the value of that particular custom field value
Same table for the denormalized field values
Table des executions. Une execution correspond à un cas de test, et ses pas d'execution correspondent à des pas de test. Pour assurer un contrôle sur les modifications de l'entité source une référence est gardée vers le cas de test source.
clé étrangère vers un ATTACHMENT_LIST, l'entité qui gère les pièces jointes.
nom du créateur de l'execution.
Date de création de cette execution. Il s'agit de la date de création de l'entrée dans la base, non d'une date métier.
the name of the dataset used
Une description associée à cet élément. Devrait être un champ texte long ou un clob.
clé primaire de l'execution. Devrait être autogénérée.
Mode d'execution de cette execution. Bien que ce champs soit caractère variable, les données réelles seront la représentation texte d'un type énuméré. C'est une copie du mode d'execution du cas de test référencé.
Status d'execution de ce plan de test. Bien que ce champs soit caractère variable, les données réelles seront la représentation texte d'un type énuméré. Sera recalculé en fonction du status de sa derniere execution
clé étrangère vers un ISSUE_LIST, l'entité qui gère les listes d'issues.
Nom du dernier utilisateur ayant execute cet instance.
Date de derniere execution de cette instance.
Nom du dernier utilisateur ayant mis à jour cet instance.
Date de dernière mise à jour de cette instance.
Le nom/label de l'élément en question.
the prerequisite for a test_case execution
a code that helps identifying that item. Note that unlike the original version the values for that column will not be unique.
the identifier of the icon to be displayed
a label to be displayed. If the item is builtin this label will be a i18n key, else the label will be displayed verbatim
a code that helps identifying that item. Note that unlike the original version the values for that column will not be unique.
the identifier of the icon to be displayed
a label to be displayed. If the item is builtin this label will be a i18n key, else the label will be displayed verbatim
Clé étrangère vers le cas de test référencé. Cette information est redondante puisque il s'agit toujours du même que celui du test plan, cependant cette information ne devant jamais évoluer il n'y a pas de risque à dénormaliser
Cette table associe une executions à ses pas d'execution. Cette table d'association existe pour ajouter un attribut d'ordre (la liste des pas executions est ordonnée). La clé primaire est ici composite, et ne doit pas être autogénérée.
clé étrangère vers la table EXECUTION.
clé étrangère vers EXECUTION_STEP
numéro d'ordre d'un pas d'execution dans la liste des pas d'executions d'une execution.
Cette table gère les pas d'execution d'une execution. Voir la table EXECUTION pour plus de détails.
action à réaliser dans ce pas d'execution.
clé étrangère vers un ATTACHMENT_LIST, l'entité qui gère les pièces jointes.
commentaire libre du recetteur.
nom du créateur du pas d'execution.
Date de création de ce pas d'execution. Il s'agit de la date de création de l'entrée dans la base, non d'une date métier.
Status de l'execution de ce pas d'execution. Bien que ce champs soit caractère variable, les données réelles seront la représentation texte d'un type énuméré.
clé primaire autogénérée.
le résultat attendu de l'action effectuée.
clé étrangère vers un ISSUE_LIST, l'entité qui gère les listes d'issues.
Nom du dernier utilisateur ayant execute cet instance.
Date de derniere execution de cette instance.
Nom du dernier utilisateur ayant mis à jour cet instance.
Date de dernière mise à jour de cette instance.
Clé étrangère vers le pas de test référencé
creating the table structure for parameterized list
a code that helps identifying that list
username of the user who created that list
the time at when that list was created
a description for that list
the ID
the label for this list. Would noly be displayed in the administration page as the name actually displayed to regular uses would depend on the role of that list on a given projet (criticality, nature etc)
username of the last user who modified one of the list attributes
Time when the list was touched last
creating the table structure for parameterized list
a code that helps identifying that item
the identifier of the icon to be displayed
whether this item is the default item for its list. Only one item per list should have it true
an ID, what did you expect ?
the position of that item in the list. Allows 'NULL' for Hibernate to work.
discriminator telling whether this item is user-made or builtin in the app. Pick one of 'USR' or 'SYS'
a label to be displayed. If the item is builtin this label will be a i18n key, else the label will be displayed verbatim
foreign key to the list this item belongs to. Allows 'NULL' for Hibernate to work.
This table maintains the mapping between an issue in Squash and an issue in the remote bugtracker
Issue's bugtracker
References the list of issue to which an issue belongs
considering the different types a bugtracker may use for its own primary keys, we use here a varchar type as it is generic enough
each Squash entity that may be attached to one or several bugs will be given an issue list. This table will maintain that list, an entry means that some entity refering to it have several.
Cette table associe un cas de test avec une liste d'execution. Elle conserve également en mémoire le status d'execution, qui devra sera mis à jour au fur et à mesure qu'une execution est ajoutée ou exécutée.
nom du créateur du testplan
Date de création du test plan. Il s'agit de la date de création de l'entrée dans la base, non d'une date métier.
Status d'execution de ce plan de test. Bien que ce champs soit caractère variable, les données réelles seront la représentation texte d'un type énuméré. Sera recalculé en fonction du status de sa derniere execution
clé primaire du test plan. Devrait être autogénérée.
Le label (duplicata du nom du cas de test) du test plan
Nom du dernier utilisateur ayant execute cet instance.
Date de derniere execution de cette instance.
Nom du dernier utilisateur ayant mis à jour cet instance.
Date de dernière mise à jour de cette instance.
Clé étrangère vers le cas de test référencé
Id de l'utilisateur assigné a ce cas de test reférenncé
Associe les executions aux test plans
clé étrangère vers la table EXECUTION
numéro d'ordre d'une execution dans la liste des test plans d'une itération.
clé étrangère vers ITEM_TEST_PLAN.
Cette table associe une iteration a ses test plans. Cette table d'association existe pour ajouter un attribut d'ordre (la liste des test plans est ordonnée). La clé primaire est ici composite, et ne doit pas être autogénérée.
clé étrangère vers la table ITEM_TEST_PLAN
numéro d'ordre d'une execution dans la liste des test plans d'une itération.
clé étrangère vers ITERATION.
clé étrangère vers un ATTACHMENT_LIST, l'entité qui gère les pièces jointes.
a reference lavel for an iteration
Association table between ITERATION and TEST_SUITE. Like in many other places here, the purpose of this association table is not to model a n-n cardinality between ITERATION and TEST_SUITE, but 1-n. We thus gain performance at the expense of the model quality.
Create KEYWORD_EXECUTION table. Update SCRIPTED_EXECUTION_EXTENDER table/column.
Create KEYWORD_TEST_CASE table. Update SCRIPTED_TC_EXTENDER table/column
Add keyword test step table
The action word which this test step uses
A keyword test step comment
A keyword test step datatable
A keyword test step docstring
A keyword test step keyword
Shared key with TEST_STEP table
As of now X_LIBRARY_PLUGINS are merged in the single table LIBRARY_PLUGIN_BINDING
This column specifies if plugin is enable or disable for a project .
ID of the library. It is explicitely nullable because hibernate will first create the row then update this column.
discriminator of the library. T: test case library, R : requirement library, C : campaign library
primary key (autogenerated)
id of the plugin. Note that those plugins aren't stored in the database and the plugin registry is purely software (it is basically based on the presence/absence of an OSGI services published by each plugin) so we cannot really enforce referential integrity. Still, although technically that column cannot be a foreign key, the application uses it as if.
This column specifies which type of plugin is used. for now only one type used: Automation.
create the table LIBRARY_PLUGIN_PROPERTY
foreign key to LIBRARY_PLUGIN_BINDING
key of this property
value of this property
Table for Milestones
Name of the milestone creator
Date of creation.
Milestone description
Term date
Milestone label
last modified by
Date of last update
Milestone range
Primary key
Milestone status
the user that own the milestone
Table for MilestoneBinding
Table for MilestoneBindingPerimeter
Creating the tables modeling the relationships between milestones and test cases, requirement versions and campaigns
foreign key to table CAMPAIGN
foreign key to table MILESTONE
Creating the tables modeling the relationships between milestones and test cases, requirement versions and campaigns
foreign key to table MILESTONE
foreign key to table REQUIREMENT_VERSION
Creating the tables modeling the relationships between milestones and test cases, requirement versions and campaigns
foreign key to table MILESTONE
foreign key to table TEST_CASE
Tables for OAuth2 Support
Tables for OAuth2 Support
Tables for OAuth2 Support
Tables for OAuth2 Support
Tables for OAuth2 Support
Tables for OAuth2 Support
Add table to handle test cases PARAMETERS
the description of the parameter
the parameter name, should be unique among parameters of the same test case
the PARAMETER primary key
the test case where the parameter is declared
foreign key to the core_party table
Table representant les projets englobants les libraries d'entite que nous utilisons.
si le projet est actif ou non
fk to the automation request library
clé étrangère vers un ATTACHMENT_LIST, l'entité qui gère les pièces jointes.
This column precises which workflow type is used.
cle etrangere de la table campaign-Library
nom du createur du projet.
Date de creation de ce projet. Il s'agit de la date de creation de l'entree dans la base, non d'une date metier.
FK FOR CUSTOM_REPORT_LIBRARY.CRL_ID
description du projet
Label du projet
Nom du dernier utilisateur ayant mis a jour cet instance.
Date de derniere mise a jour de cette instance.
nom du projet
cle primaire de la table
P: project, T: project template
foreign key to the requirement categories used in that project
cle etrangere de la table REQUIREMENT-Library
the reference to the test automation server
foreign key to the test case natures used in that project
foreign key to the test case types used in that project
cle etrangere de la table TESTCASE-Library
filter activated yes or no
unique user login
foreign key to filter
foreign key to project
The associative table TM_TA_PROJECTS is totally re-purposed as TEST_AUTOMATION_PROJECT (and the former table is ditched).
the list of approved slaves servers
the former primary key
the (friendly) alias for that TA project
the (real) name of the remote test automation project
foreign key to the automated test server
the primary key
the reference to the TM project
This table indicates which projected columns are aggregated on for a given query.
the operation applied to the column, if any.
the order in which this projected column in the returned tuple.
the custom field id for this projection column, if the referenced column is a custom field.
A label for this projected column. Will override the default label of the column prototype if non null.
foreign key to the QUERY_COLUMN_PROTOTYPE which must be aggregated on
foreign key to a QUERY_MODEL.
This table defines the columns on which one want to filter the data.
the custom field id for this filter column, if the referenced column is a custom field.
a comparison operator
foreign key to a QUERY_COLUMN_PROTOTYPE
autogenerated ID
foreign key to a QUERY_MODEL
This table holds the values used by a QUERY_FILTER_COLUMN.
a value for this filter
foreign key to QUERY_FILTER_COLUMN
This table indicates how the projected columns are ordered.
the custom field id for this filter column, if the referenced column is a custom field.
either ASC or DESC
the operation applied to the column, if any. It must mirror the operation applied to the column they reference in the projection/aggregation clause.
the order in which this ordering instruction must be treated.
foreign key to the QUERY_COLUMN_PROTOTYPE which must be ordered
foreign key to a QUERY_MODEL. Note that this is a denormalization : that value could be retrieved via the referenced projection column
This table define which columns are part of tuple returned by a query.
the custom field id for this projection column, if the referenced column is a custom field.
A label for this projected column. Will override the default label of the column prototype if non null.
the operation applied to the column, if any.
the order in which this projected column in the returned tuple.
foreign key to the QUERY_COLUMN_PROTOTYPE this projection applies to
foreign key to a QUERY_MODEL
Create new table for RemoteAutomationRequestExtender
The automation request this extender extends
Date of the last synchronisation.
Date of the last synchronisation squash to remote server.
email of the assigned
The auto-generated id
The remote issue key as generated by Jira
The Url to the remote request
The remote status as defined in the bugtracker
The values of the test case fields sent during synchronization.
The bugtracker to which the automation request is linked
this column can be set to: TO SYNCHRONIZE, DELETED, MOVED_PROJECT and MOVED_ISSUE_TYPE ; and it is updated after each synchronization.
Add a remote synchronisation table in squash tm.
This column specifies if synchronisation is enable or disable for a project
additional informations about this report
The name of this chart
parameters to generate the report
The namespace of the report plugin
foreign key to the projet
autogenerated ID
Cette table gere les exigences proprement dites. Une entree dans cette table indique que l'element reference dans la table REQUIREMENT_LIBRARY_NODE par la cle primaire (egalement cle etrangere) est de type exigence.
FK to REQUIREMENT_VERSION linking to the requirement's latest version. Should not be null but the column is nullable because of cyclic relationship between the tables.
Says whether a requirement is NATIVE or SYNCHRONIZED
cle primaire, qui est aussi une cle etrangere vers la table REQUIREMENT_LIBRARY_NODE. Ne doit donc pas etre autogeneree.
This table is the main table of the event logging system, in other words the history of a business entity. As for Squash TM version 1.1.0 and until further notice, we log here requirement modifications only. It may grows to log other entities in the future, ie test cases. Note : the application will fill this table itself, since we don't want triggers in the database.
the login of the user who generated the event
the timestamp of the log entry
the ID of the target entity. As for 1.1.0 and until further notice, the target is always a requirement version.
It is a child table of REQUIREMENT_AUDIT_EVENT. This table exists for the sole purpose of qualifying a given event in a creation event, as such its content is empty (the sheer presence of an entry in this table is sufficient)
primary key, which is also a foreign key to REQUIREMENT_AUDIT_EVENT (they share that key : do not make this table autoincrement it).
Cette table est rudimentaire. La cle primaire est simplement une cle etrangere vers la table REQUIREMENT_LIBRARY_NODE (relation qualifiante). Une entree dans cette table indique que l'element indexe par cette cle est de type repertoire.
FK to SIMPLE_RESOURCE table
cle primaire, qui est une cle etrangere vers la table REQUIREMENT_LIBRARY_NODE. Ne doit donc pas etre autogeneree.
Add a remote folder synchronisation table in squash tm.
Only one master folder should be targeted by a given synchronisation
Only one extender for any folder in Squash TM
This is a child table of REQUIREMENT_AUDIT_EVENT. This table will log updates on the target entity. Not every operations will be logged. Note 1 : As for version 1.1.0 and until further notice for the sake of simplicity we log both the former and the new value. It may change in the future. Note 2 : For technical reasons this table exists in two flavors. The twin table is REQUIREMENT_PROPERTY_CHANGE. This table will log blobs, while the other one will log standard attributes.
primary key, which is also a foreign key to REQUIREMENT_AUDIT_EVENT (they share that key : do not make this table autoincrement it).
Cette table gere les bibliotheques d'exigences. Une bibliotheque d'exigences peut contenir plusieurs repertoires et/ou exigences, ces deux entites etant regroupees sous l'appellation generique d'element de bibliotheque d'exigences (requirement library nodes).
clé étrangère vers un ATTACHMENT_LIST, l'entité qui gère les pièces jointes.
cle primaire autogeneree
Cette table associe les bibliotheques d'exigences a leur contenu (elements de bibliotheques d'exigence). Le contenu d'une bibliotheque d'exigence est arborescent et est represente suivant un patron composite (voire REQUIREMENT_LIBRARY_NODE, REQUIREMENT_FOLDER, REQUIREMENT). Par defaut la presente table peut contenir uniquement les references vers les elements fils directs; on peut aussi mettre en relation une bibliotheque d'exigence avec n'importe quel element de son contenu (quelque soit sa profondeur hierarchique) pour des raisons d'optimisation.
cle etrangere vers un noeud de la bibliotheque d'exigences.
cle etrangere vers une bibliotheque d'exigence.
Cette table represente un element (generique) faisant partie d'une bibliotheque d'exigences. Cet element generique peut representer soit un repertoire, soit une exigence. Pour cette raison, que l'utilisateur cree l'un ou l'autre cette table sera necessairement alimentee, et contiendra la cle primaire de l'element en question. Toutefois le type reel de l'element (exigence ou repertoire) n'est pas renseigne, il est necessaire de rechercher si la cle est referencee dans la table REQUIREMENT_FOLDER ou REQUIREMENT pour determiner si cet element releve de l'un ou l'autre.
nom du createur de ce cas de test.
Date de creation de cette exigence. Il s'agit de la date de creation de l'entree dans la base, non d'une date metier.
Nom du dernier utilisateur ayant mis a jour cet instance.
Date de derniere mise a jour de cette instance.
FK to the Project to which belongs this resource
cle primaire autogeneree
This is a child table of REQUIREMENT_AUDIT_EVENT. This table will log updates on the target entity. Not every operations will be logged. Note 1 : As for version 1.1.0 and until further notice for the sake of simplicity we log both the former and the new value. It may change in the future. Note 2 : For technical reasons this table exists in two flavors. The twin table is REQUIREMENT_LARGE_PROPERTY_CHANGE. This table will log standard attributes, while the other one will log blobs.
primary key, which is also a foreign key to REQUIREMENT_AUDIT_EVENT (they share that key : do not make this table autoincrement it).
This table holds the optional extension for requirement, that flags them as synchronized requirement
foreign key to the source bugtracker
the last used that synchronized that requirement with the remote manager
name of a filter (not its ID)
ID of the remote project that hosts the remote requirement
ID of the remote requirement
the url of the remote requirement
autogenerated key
foreign key to the (now synchronized) requirement
Creates REQUIREMENT_VERSION table in which we store the versions of requirements
foreign key to the info list item
Requirement category. Althought this field is a variable character, the data will be the text representation of an enumeration
Requirement criticality. Althought this field is a variable character, the data will be the text representation of an enumeration
The requirement's reference
FK to the requirement. Should not be null but is nullable because of cyclic association REQ - REQ_VER
shared key with RESOURCE table
This requirement's version number
The new table is called "REQUIREMENT_VERSION_COVERAGE"
generated surrogate key
FK to the verified requirement version
FK to the verifying test case
foreign key to the requirement_version_link_type table
foreign key for related requirement version to requirement_version table
foreign key for requirement version to requirement_version table
Only one item per list should have it true
A tree node organizes resources. These are stored in the RESOURCE table
clé étrangère vers un ATTACHMENT_LIST, l'entité qui gère les pièces jointes.
Who created this requirement's version
When this requirement's version was created
Resource's description
Who modified this requirement's version last
When this requirement's version was last modified
Resource's name
generated surrogate key
Cette table gere la hierarchie entre elements d'une bibliotheque d'exigences, associant un element fils a un repertoire parent.
cle etrangere vers le repertoire parent (il s'agit necessairement d'un repertoire).
cle etrangere vers l'element fils.
closure table for requirement library nodes. Its content is set and modified by four triggers, see changeset 'tm-1.3-feat-1112.06-mysql' or 'tm-1.3-feat-1112.06-h2'.
cle etrangere vers le noeud parent. La relation est parfois d'un noeud vers lui meme.
stores how deep is the descendant element nested in the subtree of the ancestor element
cle etrangere vers l'element fils. La relation est parfois d'un noeud vers lui meme.
Add new table for scm (source code management) server.
The kind of scm server.
The id of the scm server.
Create the scripted execution table
foreign key to EXECUTION
scriptLanguage of script
script name,by example feature name for Gherkin
autogenerated ID
Create the scripted test case table
scriptLanguage of script
the test case script
foreign key to TEST_CASE
SIMPLE_RESOURCE stores "concrete" resources with a name and a description
shared key with RESOURCE table
Adding the ability to use application-level credentials that allows Squash interact with a bugtracker on its own (ie instead of requiring the current user to authenticate).
foreign key to the server to authenticate
Foreign key to the user account that owns the credentials. A NULL value means that Squash-TM owns the credentials (app-level credentials).
the role of the content, either CRED or CONF
primary key
the credentials as an encrypted string
the version of encryption service used. Possibly the value will remain to 1 forever.
new requirement audit trail tables for synchronization events
primary key, which is also a foreign key to REQUIREMENT_AUDIT_EVENT (they share that key : do not make this table autoincrement it).
the url of the synchronized requirement at the time of creation
new requirement audit trail tables for synchronization events
primary key, which is also a foreign key to REQUIREMENT_AUDIT_EVENT (they share that key : do not make this table autoincrement it).
the url of the synchronized requirement at the time of update
Cette table gere la hierarchie entre elements d'une bibliotheque de cas de test, associant un element fils a un repertoire parent (si non NULL) ou eventuellement aucun (NULL, dans le cas ou l'element est a la racine de la bibliotheque de cas de test).
cle etrangere vers le repertoire parent (il s'agit necessairement d'un repertoire).
cle etrangere vers l'element fils.
closure table for test case library nodes. Its content is set and modified by four triggers, see changeset 'tm-1.3-feat-1112.05-mysql' or 'tm-1.3-feat-1112.05-h2'.
cle etrangere vers le noeud parent. La relation est parfois d'un noeud vers lui meme.
stores how deep is the descendant element nested in the subtree of the ancestor element
cle etrangere vers l'element fils. La relation est parfois d'un noeud vers lui meme.
Add the template_configurable_plugin_binding table.
creating table TEST_AUTOMATION_SERVER
Who created this test automation server
When was created that server
A description for the server. Since its of type 'CLOB' it might not be so short after all.
the kind of automated test server TM will deal with.
Author of last edition
Last date of edition
Should the user select which slave will run the tests (if there are some) ?
Cette table gere les cas de test proprement dits. Une entree dans cette table indique que l'element reference dans la table TEST_CASE_LIBRARY_NODE par la cle primaire (egalement cle etrangere) est de type cas de test.
Y: Yes, N: No, M: Maybe
The path to the test
foreign key to AUTOMATED_TEST_TECHNOLOGY
Mode d'execution du test case. Bien que ce champs soit caractere variable, les donnees reelles seront la representation texte d'un type enumere.
The importance of the test case
Should the importance be automatically computed
the prerequisite for a test_case
foreign key to SCM_REPOSITORY, link to associated scm repository.
foreign key to the info list item
foreign key to the info list item
cle primaire, qui est aussi une cle etrangere vers la table TEST_CASE_LIBRARY_NODE. Ne doit donc pas etre autogeneree.
Le numero de version de ce cas de test
Cette table est rudimentaire. La cle primaire est simplement une cle etrangere vers la table TEST_CASE_LIBRARY_NODE (relation qualifiante). Une entree dans cette table indique que l'element indexe par cette cle est de type repertoire.
cle primaire, qui est une cle etrangere vers la table CAMPAIGN_LIBRARY_NODE. Ne doit donc pas etre autogeneree.
Cette table gere les bibliotheques de cas de test. Une bibliotheque de cas de test peut contenir plusieurs repertoires et/ou cas de test, ces deux entites etant regroupees sous l'appellation generique d'element de bibliotheque de cas de test (test case library nodes).
clé étrangère vers un ATTACHMENT_LIST, l'entité qui gère les pièces jointes.
cle primaire autogeneree
Cette table associe les bibliotheques de cas de test a leur contenu (elements de bibliotheques de cas de test). Le contenu d'une bibliotheque de cas de test est arborescent et est represente suivant un patron composite (voire TEST_CASE_LIBRARY_NODE, TEST_CASE_FOLDER, TEST_CASE). Par defaut la presente table peut contenir uniquement les references vers les elements fils directs; on peut aussi mettre en relation une bibliotheque de cas de test avec n'importe quel element de son contenu (quelque soit sa profondeur hierarchique) pour des raisons d'optimisation.
cle etrangere vers un noeud de la bibliotheque de cas de test.
cle etrangere vers une bibliotheque de cas de test.
Cette table represente un element (generique) faisant partie d'une bibliotheque de cas de test. Cet element generique peut representer soit un repertoire, soit un cas de test. Pour cette raison, que l'utilisateur cree l'un ou l'autre cette table sera necessairement alimentee, et contiendra la cle primaire de l'element en question. Toutefois le type reel de l'element cas de test ou repertoire) n'est pas renseigne, il est necessaire de rechercher si la cle est referencee dans la table TEST_CASE_FOLDER ou TEST_CASE pour determiner si cet element releve de l'un ou l'autre.
clé étrangère vers un ATTACHMENT_LIST, l'entité qui gère les pièces jointes.
nom du createur de ce cas de test.
Date de creation de ce cas de test. Il s'agit de la date de creation de l'entree dans la base, non d'une date metier.
Une description associee a cet element. Devrait etre un champ texte long ou un clob.
Nom du dernier utilisateur ayant mis a jour cet instance.
Date de derniere mise a jour de cette instance.
Le nom/label de l'element en question.
FK to the Project to which belongs this resource
cle primaire autogeneree.
Cette table associe un cas de test a ses pas de test. Cette table d'association existe pour ajouter un attribut d'ordre (la liste des pas de test est ordonnee). La cle primaire est ici composite, et ne doit pas etre autogeneree.
cle etrangere vers la table TEST_STEP.
numero d'ordre d'un pas de test dans la liste des pas de test d'un cas de test.
cle etrangere vers TEST_CASE.
Cette table gere les pas de test d'un cas de test.
cle primaire autogeneree.
Add the table TEST_SUITE. A TEST_SUITE is basically a view on a subset of ITERATION_TEST_PLAN_ITEMs.
Who created this test suite
When this test suite was created
Who modified this test suite last
When this test suite was last modified
create table item_test_plan_test_suite
Create the table THIRD_PARTY_SERVER
the policy that decides who needs to authenticate
the protocol that should be used for that server
name of the server
primary key, autogenerated
the base url
Let's add a table VERIFYING_STEPS to hold the steps that are concerned by the requirement coverage
FK to the concerned requirement-version-coverage
FK to the concerned action test step