Validation tests

From AtoM wiki
Revision as of 14:50, 8 July 2020 by JennR (talk | contribs) (→‎ISDIAH template)

Main Page > Development > Functional testing > Validation tests

ISAD(G) template

  • The following fields in the edit screen have asterisks next to the field labels: identifier, title, dates(s), level of description, extent and medium, name of creator(s).
  • Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
  • Saving a record without a title results in the warning "Title - This is a mandatory element."
  • Saving a record with none of the date fields (start year, end year or date display) results in the warning "Date(s) - This is a mandatory element."
  • Saving a record with one of the date fields (start year, end year or date display) results in no warning about dates.
  • Saving a record without extent and medium results in the warning "Extent and medium - This is a mandatory element."
  • Saving a record without a creator when no creator has been entered at a higher level of description results in the warning "This archival description, or one of its higher levels, requires at least one creator."
  • Saving a record without a creator when a creator has been entered at a higher level of description results in no warning about creator.
  • Saving a child record with a creation start year that is earlier than the creation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
  • Saving a child record with a creation end year that is later than the creation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
  • Saving a child record with a creation start year that is the same as the creation start year for the parent record results in no warning.
  • Saving a child record with a creation end year that is the same as the creation end year for the parent record results in no warning.
  • Saving a child record with an accumulation start year that is earlier than the accumulation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
  • Saving a child record with an accumulation end year that is later than the accumulation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
  • Saving a child record with an accumulation start year that is earlier than the creation start year for the parent record results in no warning.
  • Saving a child record with an accumulation end year that is later than the creation end year for the parent record results in no warning.
  • Saving a child record with an accumulation start year that is the same as the accumulation start year for the parent record results in no warning.
  • Saving a child record with an accumulation end year that is the same as the accumulation end year for the parent record results in no warning.
  • Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
  • AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.

Test as follows:

    • A fonds cannot be a child level of a fonds
    • A fonds cannot be a child level of a series
    • A fonds cannot be a child level of a file
    • A fonds cannot be a child level of an item
    • A series cannot be a child level of a file
    • A series cannot be a child level of an item
    • A file cannot be a child level of a file
    • A file cannot be a child level of an item
    • An item cannot be a child level of an item

RAD template

  • The following fields in the edit screen have asterisks next to the field labels: title proper, level of description, physical description and scope and content. The date field is mandatory at the highest descriptive level, but not at lower levels; therefore, no asterisk appears next to the date entry field.
  • Saving a record without a date results in the warning "This archival description requires at least one date."
  • Saving a record without a title proper results in the warning "Title - This is a mandatory element"
  • Saving a record without a level of description results in the warning "Level of description - This is a mandatory element"
  • Saving a record without a physical description results in the warning "Physical description - This is a mandatory element"
  • Saving a record without a scope and content results in the warning "Scope and content - This is a mandatory element"
  • Saving a child record without a title proper results in the warning "Title - This is a mandatory element"
  • Saving a child record without a level of description results in the warning "Level of description - This is a mandatory element"
  • Saving a child record without a physical description results in the warning "Physical description - This is a mandatory element"
  • Saving a child record without a scope and content results in the warning "Scope and content - This is a mandatory element"
  • Saving a child record without a date results in the warning "This archival description requires at least one date."
  • Saving a child record with a start date prior to the parent start date results in the warning "Date(s) are not consistent with higher levels"
  • Saving a child record with an end date later than the parent end date results in the warning "Date(s) are not consistent with higher levels"
  • Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
  • AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.

Test as follows:

    • A fonds cannot be a child level of a fonds
    • A fonds cannot be a child level of a series
    • A fonds cannot be a child level of a file
    • A fonds cannot be a child level of an item

Dublin Core template

  • The following fields in the edit screen have asterisks next to the field labels: identifier, title, and relation (isLocatedAt).
  • Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
  • Saving a record without a title results in the warning "Title - This is a mandatory element."
  • Saving a record without a relation (isLocatedAt) results in the warning "Relation (isLocatedAt)-This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)."
  • Child levels created from a parent automatically inherit the relation (isLocatedAt) data.
  • If User deletes data from required fields in child level, this results in the warning: "Identifier - This is a mandatory element". "Title - This is a mandatory element." "Relation(isLocatedAt)-This is a mandatory element."

ISAAR template

  • The following fields in the edit screen have asterisks next to the field labels: type of entity, authorized form of name, dates of existence and authority record identifier.
  • Saving a record without a type of entity results in the warning "Type of entity - This is a mandatory element."
  • Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
  • Saving a record without dates of existence results in the warning "Dates of existence - This is a mandatory element."
  • Saving a record without an authority record identifier results in the warning "Authority record identifier - This is a mandatory element."
  • User is prevented from creating a relationship between an ISAAR record and itself.

ISDIAH template

  • The following fields in the edit screen have asterisks next to the field labels: identifier, authorized form of name.
  • Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
  • Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
  • Saving a record without at least one of city, country, postal code, region or street address in the contact area results in the warning "Contact information - You must at least include one of the following location or address fields: city, country, postal code, region or street address."

ISDF template

  • The following fields in the edit screen have asterisks next to the field labels: type, authorized form of name, description identifier.
  • Saving a record without a type results in the warning "Type - This is a mandatory element."
  • Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
  • Saving a record without a function description identifier results in the warning "Description identifier - This is a mandatory element."
  • User is prevented from creating a relationship between an ISDF record and itself.

Term template

  • Cannot select a broad term that is the same as a the current term
  • Cannot select a broad term that is a narrow term of the current term
  • Cannot select a related term that is the same as the current term
  • Cannot select a related term that is a broad term of the current term
  • Cannot select a related term that is a narrow term of the current term

User edit template

  • The following fields in the edit screen have asterisks next to the field labels: username, email, password, confirm password
  • Saving a record without a username results in the warning "Required" appearing above the field and the record does not save.
  • Saving a record without an email results in the warning "Required" appearing above the field and the record does not save.
  • Saving a record without a password results in the warning "Required" appearing above the field and the record does not save.
  • Saving a record without confirming password results in the warning "Your password confirmation did not match your password" and the record does not save.

Accession record edit template

  • The following fields in the edit screen have asterisks next to the field labels: acquisition date, immediate source of acquisition, location information. The record can be saved, even with a warning.
  • Saving a record without an acquisition date results in the warning "Acquisition date- This is a mandatory element"
  • Saving a record without a source of acquisition results in the warning "Source of acquisition - This is a mandatory element"
  • Saving a record without location information results in the warning "Location information - This is a mandatory element"
Retrieved from "http://wiki.accesstomemory.org/index.php?title=Development/Functional_testing/Validation_tests&oldid=2938"

Account

Page

Search