Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

add unit test coverage for PanelService

Open Beginner friendly
  • Is something wrong?
#6,262 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
typescript
Domain
frontend, testing

Research direction

Read frontend/src/app/workspace/service/panel/panel.service.ts and follow the plain describe/it/expect style in size-formatter.util.spec.ts. Add frontend/src/app/workspace/service/panel/panel.service.spec.ts, then run ng test. Done means resetPanels() and closePanels() each emit once on their own stream and never emit on the other stream.

Written by the indexing model from the issue text.

Description

starter-task
Task Summary

Add panel.service.spec.ts covering PanelService, a tiny event bus that exposes two Subject<void> streams (closePanelStream, resetPanelStream) with closePanels() / resetPanels() triggers.

Background

frontend/src/app/workspace/service/panel/panel.service.ts is a dependency-free service (instantiable directly via new PanelService()), so no TestBed wiring is required.

get resetPanelStream() { return this.resetPanelSubject.asObservable(); }
resetPanels() { this.resetPanelSubject.next(); }
get closePanelStream() { return this.closePanelSubject.asObservable(); }
closePanels() { this.closePanelSubject.next(); }

Behavior to pin

Scenario Contract
subscribe resetPanelStream, call resetPanels() subscriber fires exactly once
subscribe closePanelStream, call closePanels() subscriber fires exactly once
stream independence calling resetPanels() does not emit on closePanelStream, and vice-versa

Subscribe to the stream, invoke the trigger, and assert the emission count (e.g. increment a counter in the subscription). Follow size-formatter.util.spec.ts for the plain describe/it/expect style (ng test).

Scope

  • New spec: frontend/src/app/workspace/service/panel/panel.service.spec.ts.
  • No production-code changes.
Task Type
  • Refactor / Cleanup
  • DevOps / Deployment / CI
  • Testing / QA
  • Documentation
  • Performance
  • Other
Dominant language
Scala
Stars
316
Forks
192
Avg merge
4d 17h
Merged PRs (30d)
141

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/texera

All issues in apache/texera

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.