[SPARK-51026][CORE][TESTS] Remove the unnecessary test file StagePageSuite.scala
#49721
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.
What changes were proposed in this pull request?
This pr removes a test file
StagePageSuite.scalathat is no longer needed.Why are the changes needed?
The current
StagePageSuite.scalacontains one test case and one private method. The reasons for cleaning them up are as follows:The assertion in the test case "ApiHelper.COLUMN_TO_INDEX should match headers of the task table" was cleaned up in SPARK-44490 | [SPARK-44490][WEBUI] Remove unused
TaskPagedTablein StagePage #42085. Currently, this test case only creates aStageDataobject and anAppStatusStoreobject, with no other operations or assertions. Moreover, the creation of these objects is also covered in other test cases, such asKVStoreProtobufSerializerSuite,AppStatusStoreSuite, etc. Therefore, this is already an unnecessary test case and can be cleaned up.The private method
renderStagePagehas not been used since SPARK-21809 | [SPARK-21809] : Change Stage Page to use datatables to support sorting columns and searching #21688, so it can be cleaned up.After cleaning up the above content,
StagePageSuite.scalabecomes an empty file, so it can be completely deleted.Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GitHub Actions
Was this patch authored or co-authored using generative AI tooling?
No