Week 50. User code gets emptied at parsing
I located the problem: the code from the user was being deleted inside the exercise.py so, what I need to do now is finding the point where it gets emptied.
I located the problem: the code from the user was being deleted inside the exercise.py so, what I need to do now is finding the point where it gets emptied.
So, with the discovery of the previos week, I now can debug with more ease.
Even after using the invisibility_of_element_located function, or the selenium methods to wait for an element to be clickable, some errors still happened.
I found the reason for getting that timeout errors the previous week.
The main menu, where the exercises are collected, changed to react a while ago. So now that I have a basic functionality test working, it’s time to change th...