Here we give some hints on testing AG Grid as part of your application.
End to End (e2e) Testing Copy Link
We recommend using e2e tests to validate AG Grid as part of your application.
It is recommended to use e2e tests to validate AG Grid as part of your application. There are a number of tools available to help with this, such as Playwright, Cypress or Selenium.
e2e tests are recommended so that AG Grid is run inside a real browser. Fake browser environments (such as jsdom) can be used for simple unit testing cases, but their limitations can lead to confusing test results.
A few examples of how to use Playwright with AG Grid can be found in this GitHub Repo.
jsdom Limitations Copy Link
Test tools such as vitest, Dom Testing Library and Jest often rely on jsdom to mock the browser.
jsdom is a pure JavaScript implementation of many web standards with the goal to emulate enough of a subset of a web browser to be useful for testing. However, there are some limitations to be aware of when using jsdom.
If you are using jsdom for testing, you may encounter issues that suggest the grid is not rendering correctly. However, this is likely caused by jsdom not supporting all the features of a real browser.
The main limitations that can affect AG Grid are:
- No support for CSS layout - impacts column / row virtualisation
- No support for
innerTextproperty Issue #1245 - impacts some grid components
If you wish to use jsdom for your tests you may find the following polyfill useful if you encounter issues with missing content due to the use of innerText:
// Override the innerText setter to use textContent instead within jsdom based tests
Object.defineProperty(Element.prototype, 'innerText', {
set(value) {
this.textContent = value;
},
});
Where you implement this polyfill may vary depending on your testing setup.