Update e2e tests to use CANCER_TYPE rather than tumor type

[inodb]

There are several end-to-end tests that color scatter plots based on tumor type:

• plots_tab_scatter_plot_color_by_tumor_type
• plots_tab_scatter_plot_color_by_tumor_type_highlight_categories
• plots_tab_box_plot_color_by_tumor_type
• plots_tab_box_plot_color_by_tumor_type_highlight_categories
• plots_tab_waterfall_plot_color_by_tumor_type
• plots_tab_waterfall_plot_color_by_tumor_type_highlight_categories

See e.g. plots_tab_box_plot_color_by_tumor_type_highlight_categories:

From: https://output.circle-artifacts.com/output/job/95bd19f2-0b4e-4cc5-beab-bb20a9ec0996/artifacts/0/imageCompare.html

These don't have defined colors so the colors can change randomly. The CANCER_TYPE attribute has hardcoded colors, see e.g. AML:

from https://oncotree.info

Let's use that instead for testing

[Swayam-code]

Hey @inodb , I can take this on. I’ll update the end-to-end tests for scatter plots, box plots, and waterfall plots to use the hardcoded CANCER_TYPE attribute colors (e.g., from OncoTree, like AML's LightSalmon). This will ensure consistent and predictable color mapping across tests, avoiding random color changes. I'll ensure the updates are comprehensive and tested.

I'll be grateful, if you could assign this issue to me?

[inodb]

Thanks so much @Swayam-code ! We usually don't assign tickets outside of the core contributor team, so please go ahead. Nobody else is working on it

[rishisulakhe]

Glad to work on this issue.

[alisman]

@inodb @rishisulakhe i guess we should assume that the screeshots will be need to be updated because of the colors, right?

[inodb]

@alisman yes