-- Scenario --
You have a page element (e.g. date text) which changes regularly and causes your gemini test to flag the different date each time the 'test' command is run. This can mean you waste time looking at differences which are not bugs whilst scanning through your Gemini HTML report.
You don't want to ignore the date text element though, because if, for example, it becomes too big or too small it will mean you have a bug you want to fix.
So rather than ignoring the date text using 'ignoreElements' you want to display it as a low priority issue in your Gemini HTML report. That way you'll never miss a bug.
-- Solution --
Create a 'deprioritiseElements' function which will cause test screenshots containing 1 or more deprioritised page elements to appear below all other test screenshots in the Gemini HTML report.
Hi,
-- Scenario -- You have a page element (e.g. date text) which changes regularly and causes your gemini test to flag the different date each time the 'test' command is run. This can mean you waste time looking at differences which are not bugs whilst scanning through your Gemini HTML report.
You don't want to ignore the date text element though, because if, for example, it becomes too big or too small it will mean you have a bug you want to fix.
So rather than ignoring the date text using 'ignoreElements' you want to display it as a low priority issue in your Gemini HTML report. That way you'll never miss a bug.
-- Solution -- Create a 'deprioritiseElements' function which will cause test screenshots containing 1 or more deprioritised page elements to appear below all other test screenshots in the Gemini HTML report.