| Age | Commit message (Collapse) | Author |
|
- using webmock instead of mocking Net::HTTP
therefore removing the connascence between the spec and the
HTTP lib used in the implementation, thank you Teddy
|
|
|
|
|
|
Return `true` from this method by default. If the `#update` call fails,
then it will return `false`, but in all other cases, we should return
`true`. That way, when the
`Api::V1::ComplianceCheckSetsController#validated` endpoint is called,
it will respond with the `ComplianceCheckSet` object instead of:
{"status":"error","messages":[]}
with no error messages.
Refs #4757
|
|
If any associated resources have the "IGNORED" status, this shouldn't
affect the outcome of a "successful" status. Allow the
`ComplianceCheckSet` to be "successful" even if some `Resource`s are
"IGNORED".
Refs #4757
|
|
We should return the result of the `ActiveRecord` `#update` call, so
that we can determine if there was an error saving the
`ComplianceCheckSet` record.
Refs #4757
|
|
This reverts commit b7477e28f90c961079c7b12c4992071cbc11b2d6.
This logic isn't right. We should return true/false based on the result
of `update`, as in, whether the value was able to be updated, instead of
on the contents of the status.
|
|
Ensure that `#update_status` always returns a boolean value. We'll be
using this to determine whether the updated status was 'successful' or
not. Hmmm. Wait. That's not right. We want to return true from the
update, we don't care about the status. The error case should be when
the `update` fails. Darn.
Refs #4757
|
|
Move the successful `ComplianceCheckResource`s to the end so that these
tests fail if we don't wait until the end of a loop through the resoures
before updating the status to 'successful'.
Refs #4757
|
|
Add test cases for status update when `ComplianceCheckResource` are
"ERROR" and "WARNING". If a single Resource is "ERROR" or "WARNING",
then the `ComplianceCheckSet` becomes "failed" or "warning".
Refs #4757
|
|
Initial spec that checks the correct status field change when all
`ComplianceCheckResource`s are successful.
Refs #4757
|
|
|
|
|
|
|
|
CR 2nd part
- typos
- unnecessary `class: Referential` removed from referentials_factory
- regrouping of referential_suite related model specs
|
|
CodeReview:
- Exchange fr and en translation files for referential_suites
- Consistent usage of `jeu de donées` and `espace de travail` dans les *fr.yml
Fixes: #4802@0.2h; Replaying former work. To identify spec regression
Step 3: Added validation of reference_suite#new/current
Made all specs pass
|
|
Step 2: Added validation of reference->workbench->organisation consistency
Made all specs pass
Chased bug #4826
|
|
ComplianceControl.subclass_patterns [amend me] [skip-ci]
|
|
DB Setup for specs
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Validation implemented for min_max_values with correct I18n'd error messages
Applied to: VehicleJourneyControl::Speed & GenericAttributeControl::MinMax
|
|
GenericControlAttribute validation speced for
- MinMax
- Pattern
|
|
validation, compliance_control module
|
|
Nullified ComplianceCheck STI column
speced and implemented via `self.inheritance_column = nil`
|
|
DONE:
- Copied all node atts for ComplianceChecks
- Migration of CompliancCheck#criticity int -> string
TODO:
- Check what to do with attribute ComplianceCheck#type
|
|
|
|
|
|
Specs and implements coherent direct and indirect ComplianceControlSet parentship for ComplianceControls
|
|
for name
|
|
the sorted transport modes and submodes
|
|
|
|
4627 compliance fix class vars
|
|
All implemented as class methods
|
|
- All Specs and Factories implemented
- Fixing More Typos in dir/file names and incorrect module names; long live copy and paste
|
|
- Working on factories
- Scaffolding out specs
- Fixing typos in dir struct and class names for routing_constraint_zone_control
|
|
- setting up a CCCLD subdir struct for CCCLD related tests
- removed all occcurances of `@@default_criticity`
|
|
|
|
- Rebase on udated master
- Removal of `default_criticity` from ComplianceControl Class Level Defaults
- Refactoring of specs to allow usage of the same shared examples (given that more models need to undergo the same refact)
|
|
Class Methods replace Class Attributes
|
|
Comprehensive Tests for ComplianceControl Class Level Default Attributes
|
|
Got some data_modifier support for attribute generation w/w-o defaults for model tests generic_attribute_control
|
|
Put old behavior under tests, thusly also showing the motivation of this ticket.
|
|
|