Assembly Line is now trying to show the error to the developer in a friendly way. Because of that, ALKiln does not detect that an error has happened. I believe the AL screen id is "custom error action". We need to detect that and get the error from the right element (it's still there, just hidden in collapsed content).
If we expand the collapsed content, will that show the full error or does it make you scroll? If the latter, that's a shame. We'll have to think what to do about that because we can't take a screenshot of that whole thing, at least not without changing the DOM to do it. Maybe we just have to leave the developer to get to that screen themselves :/ [That's a shame when something is going wrong with the tests themselves and it's therefore impossible to recreate manually. Right now, that only seems to be happening with this code caching problem and we're working on that, but who knows what'll come up in the future.]
Assembly Line is now trying to show the error to the developer in a friendly way. Because of that, ALKiln does not detect that an error has happened. I believe the AL screen id is "custom error action". We need to detect that and get the error from the right element (it's still there, just hidden in collapsed content).
If we expand the collapsed content, will that show the full error or does it make you scroll? If the latter, that's a shame. We'll have to think what to do about that because we can't take a screenshot of that whole thing, at least not without changing the DOM to do it. Maybe we just have to leave the developer to get to that screen themselves :/ [That's a shame when something is going wrong with the tests themselves and it's therefore impossible to recreate manually. Right now, that only seems to be happening with this code caching problem and we're working on that, but who knows what'll come up in the future.]