Adding Test in frontend components

[Claudio-code]

Issue #1184

Flows to be tested

• Login redirect component
• Logout Button in header

[razzeee]

Great work, other then the mentioned comments, I think this misses one crucial thing. It needs to be added to the github pipeline. Maybe as a new pipeline step, so that we can validate these pass on every merge.

[Claudio-code]

Cool i make adjustments during the week

• We could also check for the avatar icon with user name here
• Check the error test on the component
• Add mock global to react-i18next
• Remove all @ts-ignore
• In logout test add check if have login button
• Add tests in github pipeline

[Claudio-code]

@razzeee I made the adjustments if you can review again

[razzeee]

Hrm, seems like it's not running on our CI

[Claudio-code]

it seems that jest is giving an error because of the typescript, I will try to adjust the configuration.

jestjs/jest#11453

i dont know how resolve it, tried rollback version and all settings but not work

[razzeee]

I guess we're running into vercel/next.js#40183

[Claudio-code]

I'm trying to apply the issue solution, but it's hard to find packages that use esm

[razzeee]

It also makes it sound like it's an regression on their end, so maybe if they fix it upstream we could wait for it.
I guess we should test if the downgrade like someone suggests in the issue helps in our case.

[Claudio-code]

I tried downgrading jest to 27 and next to 13.2 and 13.1 don't work, but I if you remove node_modules and yarn.lock works but if you remove just remove node_modules not works, I don't know why