angular-testing-library icon indicating copy to clipboard operation
angular-testing-library copied to clipboard

🐙 Simple and complete Angular testing utilities that encourage good testing practices

Results 21 angular-testing-library issues
Sort by recently updated
recently updated
newest added

Hi I started migrating some components to signal based `input` and `model` functions. Unfortunately, that causes typing issues. RenderComponentOptions declares `componentInputs?: Partial | { [alias: string]: unknown };`, which resolves...

## Context I think that there is some pains in spying on the output of a component, which is typified by the fact that you have to use type assertions...

ATL depends on TL/dom directly, but TL/user-event depends on that via `peerDependencies`. https://github.com/testing-library/angular-testing-library/blob/main/projects/testing-library/package.json#L38 https://github.com/testing-library/user-event/blob/main/package.json#L73 In my project, after upgrading ATL to v16, that difference occurred version conflict errors at test....

Using `on` should also work with template renders. https://github.com/testing-library/angular-testing-library/blob/ef521727d9a5a60a998e2ef5f5406400be2a9a0c/apps/example-app/src/app/examples/02-input-output.spec.ts#L35C1-L60C4 @mumenthalers do you have an idea how this can work?

I am currently introducing testing-library for angular with vitest at our company and learned that while there is the very handy `render()` function in testing-library, an alternative for testing services...

I was looking for an example on testing an ag-grid custom cell renderer used in an angular application.

The closest I'm seeing is this example, but it has some issues: > https://github.com/testing-library/angular-testing-library/blob/main/apps/example-app/src/app/examples/22-signal-inputs.component.spec.ts 1. Only `model` can be updated, which would require us to change our components from `input`...