awesomsauce! but is there a way in debug mode to test out different selectors? like get text from an element on the page or check if perhaps another selector would fit better while the test is paused?
In debug mode, all the usual commands work. Eg. Use `self.is_element_visible("SELECTOR")` to find out if a selector is visible, etc. `self.get_text("SELECTOR")` to get text from a selector, and all the other methods.
That depends when you want the breakpoint to occur. ``--pdb`` for a breakpoint on exception. ``--trace`` for a breakpoint immediately after tests start. ``ipdb.set_trace()`` for a specific location. It can be combined with IDE breakpoints. You have options.
Looks like some nice feature additions for debugging tests. Thanks.
Holy Tabs!! Thanks for the video
Thank you michael, waiting for more tutorial
awesomsauce! but is there a way in debug mode to test out different selectors? like get text from an element on the page or check if perhaps another selector would fit better while the test is paused?
In debug mode, all the usual commands work. Eg. Use `self.is_element_visible("SELECTOR")` to find out if a selector is visible, etc. `self.get_text("SELECTOR")` to get text from a selector, and all the other methods.
@@MichaelMintz ah! absolutely fantastic. tnx!
Thank you for the tutorial! When would you use this over breakpoints with an IDE like PyCharm?
That depends when you want the breakpoint to occur. ``--pdb`` for a breakpoint on exception. ``--trace`` for a breakpoint immediately after tests start. ``ipdb.set_trace()`` for a specific location. It can be combined with IDE breakpoints. You have options.