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
I have a proposal in case is not contemplated yet. I've run into an issue on CI that didn't happen on my local dev environment. It turned out to be completely my fault but maybe wallaby could have give some extra information.
One feature test was failing to find elements that in fact were there. As I've said, everything was running fine on my machine™ so this was odd, until I've realized what the problem was.
Those elements are empty <div> that are converted to grid elements after applying some CSS, so in case of a missing stylesheet those elements will not be visible at all, and I forgot to build the assets with webpack on CI environment, so no styles were applied.
If wallaby had complained or at least warned about that 404 error when loading the CSS resource, I'd had a hint pointing in the right direction.
Having an option to make wallaby output network errors after loading a page would be helpful in similar scenarios.
Test Code & HTML
defmoduleHeroesWeb.AcceptanceTestdouseHeroesWeb.BrowserCase,async: true@moduletag:browserimportWallaby.Query,only: [css: 2]@gamegame_path(@endpoint,:index)feature"When a browser opens the game endpoint the board grid is loaded",%{session: session}doApplication.put_env(:heroes_server,:board,GameBoards.Oblivion)session|>visit(@game)|>assert_has(css("#grid .cell",count: 48))|>assert_has(css(".cell.wall",count: 7))endend
<section><h1>Heroes Board Game</h1><divid="grid"><divclass="cell"></div><divclass="cell"></div><divclass="cell"></div><divclass="cell"></div><divclass="cell wall"></div><divclass="cell"></div><!-- and so on ... --></section>
The text was updated successfully, but these errors were encountered:
Issue
I have a proposal in case is not contemplated yet. I've run into an issue on CI that didn't happen on my local dev environment. It turned out to be completely my fault but maybe wallaby could have give some extra information.
One feature test was failing to find elements that in fact were there. As I've said, everything was running fine on my machine™ so this was odd, until I've realized what the problem was.
Those elements are empty
<div>
that are converted to grid elements after applying some CSS, so in case of a missing stylesheet those elements will not be visible at all, and I forgot to build the assets with webpack on CI environment, so no styles were applied.If wallaby had complained or at least warned about that 404 error when loading the CSS resource, I'd had a hint pointing in the right direction.
Having an option to make wallaby output network errors after loading a page would be helpful in similar scenarios.
Test Code & HTML
The text was updated successfully, but these errors were encountered: