Updated test files: - Generated empty 181 file with the new CategoryTypeColumns - Updated the 173 testfile to have wave conditions calculations with different normsWTI-1706
Updated test files for ReadExtensions of the WaveConditionsCalculations: - Added asserts to verify the reference dependent output remains null when the entity has null valuesWTI-1706
Updated ReadExtensions for StabilityStoneCover: -- Cleaned up tests, replaced testcase data with random generators and a separate test asserting NaN / NULL conversions -- Added functionality to read CategoryTypeWTI-1706
Updated CreateExtensions for StabilityStoneCover: -- Cleaned up tests, replaced testcase data with random generators and a separate test asserting NaN / NULL conversions -- Added functionality to write CategoryType to entityWTI-1706
Updated ReadExtensions for WaveImpactAsphaltCover: -- Cleaned up tests, replaced testcase data with random generators and a separate test asserting NaN / NULL conversions -- Added functionality to read CategoryTypeWTI-1706
Updated CreateExtensions for WaveImpactAsphaltCover: -- Cleaned up tests, replaced testcase data with random generators and a separate test asserting NaN / NULL conversions -- Added functionality to write CategoryType to entityWTI-1706
Updated ReadExtensions for GrassCoverErosionOutwards: - Cleaned up tests, replaced testcase data with random generators and a separate test asserting NaN / NULL conversions - Added functionality to Read CategoryTypeWTI-1706
Updated CreateExtensions for GrassCoverErosionOutwards: - Cleaned up tests, replaced testcase data with random generators and a separate test asserting NaN / NULL conversions - Added functionality to write CategoryTypeWTI-1706
Updated database design to include columns related to the category type: - Regenerated .sql file and corresponding Ringtoets.rtd - Regenerated entitiesWTI-1706
Cleaned up test projects: - Renamed FullTestProjects to MigrationTestProjects, as they do not represent a full project that is configured with all options.WTI-1657
Cleaned up test projects: - Test projects should only contain the information that is necessary to prove that relevant migration items for that version was performed. Due to chaining it is not necessary to repeat this validation for subsequent projectsWTI-1657
Adjusted migration for the grass cover erosion outwards (GCEO) wave condition calculations: - Translated the old GCEO hydraulic boundary location (HBL) PKs to the new HBL PKs on assessment section based on the LocationID of a HBL and its corresponding assessment section. -- Introduced a lookup table, as these translations happen on multiple spots - Adjusted test project to prove the translations are made correctlyWTI-1657
Adjusted JOINS on the sourceproject for the Hydraulic Boundary Location of Grass Cover Erosion Outwards: - Do not join on the PK of the HBL entries, because these can be different between grass outwards and the hbls on assessment section level, instead join on the LocationID and the containing assessment section -- Adjusted migration logic for the outputs -- Adjusted migration logic for the HBL entries of grass cover erosion outwards --> take the HydraulicLocationEntityId as leading PK - Adjusted test files to represent the following scenarios situation: -- An HBL on the grass cover erosion failure mechanism that has a PK corresponding with a HBL that is not in the same assessment section -- Two HBLs on the grass cover erosion failure mechanism in the same assessment section that differs from the PKs of the HBLs on the assessment sectionWTI-1657
Adjusted JOINS on the sourceproject for the Hydraulic Boundary Locations of Grass Cover Erosion Outwards: - Do not join on the PK, because these can be different between grass outwards and the hbls on assessment section level, instead join on the LocationID and the containing assessment sectionWTI-1657
Added missing EF and SQLite references to the Application.Ringtoets.csproj: - This was done for clarity sake, because the app.config file depends on these references -- Note that the solution still worked without explicitly adding these references, because it was build and put together in a single folder with all the other dependencies that are dependent on EF and SQLite. As a consequence, EF and SQLite was always present when running the solution.Paired with ~carloslubbersWTI-1663
