1) It rearranges the tests in spec/features/support/shared_examples so that they are within folders that relate to specific areas of the code, like "report_checks", "staff_code_checks", and "in_house_repair_checks". This is to acknowledge that creating an in-house repair
isn't exactly "record creation" because the treatment record and conservation record aren't being created, and
isn't exactly "record editing" because we are creating a new object "in-house repair".
2) It adds tests for creating and deleting an in-house repair. Only the admin and standard user are given tests related to in-house repairs because the read-only users had this addressed in the shared example it_behaves_like 'can read but not edit conservation records' (renamed from displays conservation records for read-only users correctly).
3) It does NOT test in-house record editing because that functionality is not currently present in the code.
This PR does two things.
1) It rearranges the tests in spec/features/support/shared_examples so that they are within folders that relate to specific areas of the code, like "report_checks", "staff_code_checks", and "in_house_repair_checks". This is to acknowledge that creating an in-house repair
2) It adds tests for creating and deleting an in-house repair. Only the admin and standard user are given tests related to in-house repairs because the read-only users had this addressed in the shared example
it_behaves_like 'can read but not edit conservation records'(renamed fromdisplays conservation records for read-only users correctly).3) It does NOT test in-house record editing because that functionality is not currently present in the code.