You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on the tests, I found out LAN 114 uses the gnome-software tag while every other episode uses the tag gnome software. This inconsistency messes with the e2e testing I am working on because the tag page renders the title as gnome-software when my test is looking for gnome software due the tag having a space in all other episodes.
While I am not sure this is the only instance of this happening. This is only instance I have come across so far. The quick fix is update LAN 114 to use gnome software as the tag. But this does not stop this from happening again in the future.
Looking for ideas on how we could force a maybe force a standardization with automation. This is a tricky topic due instances of tags having dashes making perfect sense in certain cases. What do other people think?
The text was updated successfully, but these errors were encountered:
Since PR #507 was merged, spaces were replaced with "-" on tags URLs. LAN 114 uses the tag gnome-software but the other 5 episodes use gnome software as the tag. So when you go to the tag page, the title says gnome-software which messes with the tag testing I am trying to do. When testing tags with spaces.
URL
https://www.jupiterbroadcasting.com/show/linux-action-news/114/
On what type of device(s) did you see this bug?
Desktop
On which browser(s) are you seeing the problem?
Chrome
Other Browser
No response
Summary
While working on the tests, I found out LAN 114 uses the
gnome-software
tag while every other episode uses the taggnome software
. This inconsistency messes with the e2e testing I am working on because the tag page renders the title as gnome-software when my test is looking for gnome software due the tag having a space in all other episodes.While I am not sure this is the only instance of this happening. This is only instance I have come across so far. The quick fix is update LAN 114 to use
gnome software
as the tag. But this does not stop this from happening again in the future.Looking for ideas on how we could force a maybe force a standardization with automation. This is a tricky topic due instances of tags having dashes making perfect sense in certain cases. What do other people think?
The text was updated successfully, but these errors were encountered: