[#13324] Migrate InstructorCoursesPage to SQL-based version #13414
+466
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #13324
Description
This PR creates the SQL-based PageObject for the
InstructorCoursesPageto support the ongoing migration to the SQL backend.I have implemented
InstructorCoursesPageSql.java, mirroring the logic of the existingInstructorCoursesPage.javabut adapted to interact with SQL entities.Changes
InstructorCoursesPageSqlinteammates.e2e.pageobjects.teammates.storage.sqlentity.Courseinstead ofCourseAttributes.course.getId()as the SQL entity retains the String-based ID as the primary key.org.junit.jupiter.api.Assertions) to align with modern project standards.Verification
./gradlew compileTestJava.InstructorCoursesPage.javaimplementation.