4 ms·
We had them, then stopped maintaining them when the development speed was to high. Now (years later) we have a subset of the original tests to ensure the most
by pintxo 7y ago
We had them, then stopped maintaining them when the development speed was to high.
Now (years later) we have a subset of the original tests to ensure the most crucial processes are regression tested.
My experience is that it's a lot harder for these tests to find the right balance and depth than for unit or even other integration tests.
As already said, it's good to consistently have ids on relevant elements, as otherwise the test code complexity grows significantly.
- Ididntdothis 7y ago"As already said, it's good to consistently have ids on relevant elements, as otherwise the test code complexity grows significantly. " Life is definitely much easier if the devs set up their pages to be automation friendly. I view this as a prerequisite. Otherwise tests can get nightmarish complexity.
- ethbro 7y agoHere's looking at you, Material UI. (And almost any vendor-GUI-framework-in-a-box solution) :/