The Scenario:
Recently, our team made the switch from custom tables to Angular UI grid, which promised enhanced stability and an array of features.
Although the official Angular UI grid page boasts about its "e2e testing integration", we are encountering difficulties in getting it to function as intended.
It seems that the concept of "e2e testing integration" revolves around two helper files: gridTestUtils
and gridObjectTestUtils
.
However, there are several issues at play here:
- These helper files are not inclusive within the
angular-ui-grid
module itself nor available as a standalone library, thus necessitating manual creation by copying their current contents locally. - All helper functions seem to require pre-existing knowledge of a grid ID, whereas our grids have auto-generated IDs courtesy of
angular-ui-grid
itself, leading us to locate grids using alternative identifiers.
Conversely, the methods provided in these helper files such as resizeHeaderCell()
and shiftClickHeaderCell()
could prove incredibly useful and efficient for testing purposes.
The Query:
Are there standard practices for testing angular UI grids, and has anyone successfully integrated e2e testing with the library utilizing the aforementioned helper functions?