The following scenarios test for error conditions where the user will receive an error or warning as a result of an action. These scenarios are very important to prevent invalid exceptions on submission and prevent users from submitting invalid information. E.g. without the correct validation, a company name that contains a country name could be rejected if the error condition doesn’t show up on the screen.
Scenario: C001 Error Condition TC 001 Validate Name A public company must include at the end of its name the word LIMITED
#Scenario Type Functional Test
#Scenario Description Validate error message is displayed when a public company does not include at the end of its name the word 'LIMITED'
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF
#Catalogue Version 1.2
Scenario: C001 Error Condition TC 002 Validate Name A public company must not include the word PROPRIETARY in its name
#Scenario Type Functional Test
#Scenario Description Validate error message is displayed when a public company name includes the word 'PROPRIETARY'
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF
#Catalogue Version 1.2
Scenario: C001 Error Condition TC 003 Validate Name A private company must include at the end of its name the phrase PROPRIETARY LIMITED
#Scenario Type Functional Test
#Scenario Description Validate error message is displayed when a private company name does not include the word 'PROPRIETARY LIMITED' at the end of its name
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF
#Catalogue Version 1.2
Scenario: C001 Error Condition TC 004 Validate Name The proposed name you have entered contains the word prohibited word which is a prohibited word within the Proposed Name of a local or external company
#Scenario Type Functional Test
#Scenario Description Validate error message is displayed when proposed name contains the a prohibited word
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF
#Catalogue Version 1.2
Scenario: C001 Error Condition TC 005 Validate Name Display the standard Verne warning message where restrictive word s is being used within the Proposed Name of a local or external company
#Scenario Type Functional Test
#Scenario Description Validate warning message is displayed when the proposed name contains the restricted word
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF
#Catalogue Version 1.2
Scenario: C001 Error Condition TC 006 Validate Name Perform the standard Verne identical name check against the Companies Register for currently registered transitional
#Scenario Type Functional Test
#Scenario Description Validate error message is displayed when the proposed name is identical to a currently \ registered, transitional, or pending name.
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF Note: This check does not include the suffix.
#Catalogue Version 1.2
Scenario: C001 Error Condition TC 007 Validate Name Perform the standard Verne almost identical name check against the currently registered transitional and pending and issue a soft warning message the user will be allowed to proceed where a match is found
#Scenario Type Functional Test
#Scenario Description Validate warning message is displayed when the proposed name is almost identical to a currently \ registered, transitional, or pending name.
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF Note: This check does not include the suffix.
#Catalogue Version 1.2
Scenario: C001 Error Condition TC 008 Validate Name Perform the standard Verne identical name check against the currently registered returned for a resubmission or pending Reserved names any and issue a hard message where a match is found
#Scenario Type Functional Test
#Scenario Description Validate error message is displayed when proposed name is identical to a currently registered, returned for resubmission, or pending Reserved names
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF Note: This check does not include the suffix.
#Catalogue Version 1.2
Scenario: C001 Error Condition TC 009 Validate Name Perform the standard Verne almost identical name check against the currently registered returned for a resubmission or pending Reserved names including Reserved Business Names any and issue a soft warning message
#Scenario Type Functional Test
#Scenario Description Validate warning message is displayed when the proposed name is almost identical to a currently registered, returned for resubmission, or pending Reserved names (including Reserved Business Names)
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF Note: This check does not include the suffix.
#Catalogue Version 1.2
Scenario: C001 Error Condition TC 010 Validate Name Perform the standard Verne identical name check against the currently ceased within last 3 months Business names and issue an error message where a match is found
#Scenario Type Functional Test
#Scenario Description Validate error message is displayed when the proposed name is identical to Business name ceased within the last 3 months
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF Note: This check does not include the suffix.
#Catalogue Version 1.2
Scenario: C001 Error Condition TC 011 Validate Name Perform the standard Verne identical name check against the currently registered transitional or pending Business names and issue an error message where a match is found
#Scenario Type Functional Test
#Scenario Description Validate error message is displayed when the proposed name is identical to a currently registered, transitional or pending Business names
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF Note: This check does not include the suffix.
#Catalogue Version 1.2
Scenario: C001 Error Condition TC 012 Validate Name Perform the standard Verne almost identical name check against the currently registered transitional or pending Business names and issue a soft warning message
#Scenario Type Functional Test
#Scenario Description Validate warning message is displayed when the proposed name is almost identical to a currently registered, transitional or pending Business names
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF Note: This check does not include the suffix.
#Catalogue Version 1.2
Scenario: C001 Error Condition TC 013 Validate Name Perform the standard Verne identical name check against the current Trademarks database any and issue an error message where a match is found
#Scenario Type Functional Test
#Scenario Description Validate error message is displayed when proposed name is identical to a current Trademark
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF Note: This check does not include the suffix.
#Catalogue Version 1.2
Scenario: C001 Error Condition TC 014 Validate Name Perform the standard Verne almost identical name check against the current Trademarks database any and issue a soft warning message the user will be allowed to proceed where a match is found
#Scenario Type Functional Test
#Scenario Description Validate warning message is displayed when the proposed name is almost identical to a current Trademark
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF Note: This check does not include the suffix.
#Catalogue Version 1.2.
Scenario: C001 Error Condition TC 015 Validate Name Allow the previous name for re-use after 3 months
#Scenario Type Functional Test
#Scenario Description Validate the previous name can be used as the Proposed Name after 3 months
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF
#Catalogue Version 1.2.
Scenario: C001 Error Condition TC 016 Validate Name Allow the previous name for re-use after 3 months 1 day
#Scenario Type Functional Test
#Scenario Description Validate the previous name can be used as the Proposed Name after 3 months + 1 day
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF
#Catalogue Version 1.2.
Scenario: C001 Error Condition TC 017 Validate Name Do not allow the previous name to be reused after 3 months 1 day
#Scenario Type Functional Test
#Scenario Description Validate the previous name cannot be used as the Proposed Name after 3 months - 1 day
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF
#Catalogue Version 1.2.
Scenario: C001 Error Condition TC 018 Validate Name on the selection of Validate Name button do the checks above
#Scenario Type Functional Test
#Scenario Description Validate 'Validate Name' button perform system name checks
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF
#Catalogue Version 1.2.
Scenario: C001 Error Condition TC 019 Validate Name on form submission do the checks above
#Scenario Type Functional Test
#Scenario Description Validate on the submission system performs system name checks
#Pre Conditions: The user must be logged in with valid credentials, service is started
#Test Data Requirement:
#User Role: IND User, ORG User, Internal User
#REQ-REF
#Catalogue Version 1.2.0
