THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The following end-to-end test scenarios will be carried out for the UI:
- Data skew score is accurately presented on the Job Graph vertices and is refreshed, similar to the existing Backpressure and Busy metrics
- The new Data Skew tab lists the operator in descending order of their data skew score
- This tab shows the data skew score for operators from the beginning of the job. That is, it does not show the live/current data skew score.
- Data skew score is refreshed every time the tab is loaded
- A refresh button similar to that on the Checkpoint page can be used to refresh the data on screen
- Given a job with no or close to 0 data skew, all operators show a data skew score of 0% or a figure close to 0%
- Given a job with an operator that is suffering from data skew of about 50%, the figure is accurately reflect on the operator on the Flink job graph
- Above scenarios are tested under the new Data skew tab
- Operators are sorted according to their data skew score
- Impact on UI
- Page load speed comparison (there should not be extra delay to the job graph page load time). If delay turns out to be unavoidable, this should be documented as a side-effect
- Monitor page memory usage and ensure there is no memory leak or memory usage is not noticeably higher than before. If noticeable increase in memory is unavoidable, document this as a side-effect
Data Skew Score Tests
The following behaviour will be unit and end-to-end tested:
...