Question about unittesting a directive with HostListener(keydown)

[revenger1986]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[x] Support request
[ ] Other... Please describe:

Current behavior

I'm not here to report an issue, but I was hoping that someone could point me in the correct direction.
At the moment i'm trying to make a unit test for a custom directive which has a Hostlistener(keydown).

So this is a simplified version of the HostListener in my directive.

@HostListener('keydown', ['$event'])
  public onKeyDown(event: KeyboardEvent): void {
   
    if ((event.key === '2' ) 
    { 
       event.preventDefault();
       return; 
   }
}

In my unittest (i'm using jest and ofc specator) i try to do this.

beforeEach(() => {
   spectator = createDirective(`<input type="text" value="0" myDirective>`);
});

it('should allow 1', () => {
   const event = new KeyboardEvent('keydown', { code: '49', key: '1'});
   spectator.directive.onKeyDown(event);
        
   expect(spectator.element).toHaveValue("1");
});

When running the unit test the value of the spectator.element is still the initial value 0. I understand that this hostlistener is not changing the value directly, but I was expecting that when the code didn't hit the event.preventDefault() the value of the input would still change.
How would you advice me to test this?

Environment

Angular version: 10.0.2

Browser:
- [x] Chrome (desktop) version XX

[srenbo]

Hi there!
I have the exact same problem.
Does anyone have a solution?
Thx!