[I] Three dashboard component specs never call fixture.detectChanges() [texera]

["Yicong-Huang (via GitHub)" <gi...@apache.org>]

Yicong-Huang opened a new issue, #5180:
URL: https://github.com/apache/texera/issues/5180

   ### Task Summary
   
   Three frontend component specs construct a `ComponentFixture` via `TestBed.createComponent` but never call `fixture.detectChanges()`, so the template's creation pass never runs. The corresponding `.component.html` files stay at 0 % coverage even though each spec passes green. This contradicts golden rule #1 in `frontend/AGENTS.md` and the mental model documented in `frontend/TESTING.md` §"Why detectChanges() is the coverage switch".
   
   Affected specs:
   
   - `frontend/src/app/dashboard/component/user/list-item/list-item.component.spec.ts`
   - `frontend/src/app/dashboard/component/user/share-access/share-access.component.spec.ts`
   - `frontend/src/app/dashboard/component/user/user-dataset/user-dataset-explorer/user-dataset-file-renderer/user-dataset-file-renderer.component.spec.ts`
   
   ### Task Type
   
   - [x] Testing / QA


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Three dashboard component specs never call fixture.detectChanges() [texera]

["Yicong-Huang (via GitHub)" <gi...@apache.org>]

Yicong-Huang closed issue #5180: Three dashboard component specs never call fixture.detectChanges()
URL: https://github.com/apache/texera/issues/5180


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org