SigNoz is an open-source, OpenTelemetry-native observability platform for your team and their AI agents. Get logs, metrics, and traces in one tool with features like APM, distributed tracing, log management, infra monitoring, etc. Combined with SigNoz MCP and a native AI teammate (in SigNoz Cloud) it helps you build more resilient apps.
TypeScript apmapplication-monitoringdistributed-tracinggogood-first-issuejaegerloglogsmetricsmonitoringnextjsobservabilityopen-sourceopentelemetryprometheusreactreactjsself-hostedtracingtypescript
Testing Guide
Tech Stack
- React Testing Library (RTL)
- Jest (runner, assertions, mocking)
- MSW (Mock Service Worker) for HTTP
- TypeScript (type-safe tests)
- JSDOM (browser-like env)
Unit Testing: What, Why, How
- What: Small, isolated tests for components, hooks, and utilities to verify behavior and edge cases.
- Why: Confidence to refactor, faster feedback than E2E, catches regressions early, documents intended behavior.
- How: Use our test harness with providers, mock external boundaries (APIs, router), assert on visible behavior and accessible roles, not implementation details.
Basic Template
import { render, screen, userEvent, waitFor } from 'tests/test-utils';
import { server, rest } from 'mocks-server/server';
import MyComponent from '../MyComponent';
describe('MyComponent', () => {
it('renders and interacts', async () => {
const user = userEvent.setup({ pointerEventsCheck: 0 });
server.use(
rest.get('*/api/v1/example', (_req, res, ctx) => res(ctx.status(200), ctx.json({ value: 42 })))
);
render(<MyComponent />, undefined, { initialRoute: '/foo' });
expect(await screen.findByText(/value: 42/i)).toBeInTheDocument();
await user.click(screen.getByRole('button', { name: /refresh/i }));
await waitFor(() => expect(screen.getByText(/loading/i)).toBeInTheDocument());
});
});
.cursorrules (Highlights)
- Import from
tests/test-utilsonly. - Prefer
userEventfor real interactions; usefireEventonly for low-level events (scroll/resize/settingscrollTop). - Use MSW to mock network calls; large JSON goes in
mocks-server/__mockdata__. - Keep tests type-safe (
jest.MockedFunction<T>, avoidany). - Prefer accessible queries (
getByRole,findByRole) before text anddata-testid. - Pin time only when asserting relative dates; avoid global fake timers otherwise.
Repo-specific reasons:
- The harness wires Redux, React Query, i18n, timezone, preferences, so importing from RTL directly bypasses critical providers.
- Some infra deps are globally mocked (e.g.,
uplot) to keep tests fast and stable. - For virtualization (react-virtuoso), there is no
userEventscroll helper; usefireEvent.scrollafter settingelement.scrollTop.
Example patterns (from components/QuickFilters/tests/QuickFilters.test.tsx)
MSW overrides per test:
server.use(
rest.get(`${ENVIRONMENT.baseURL}/api/v1/orgs/me/filters/logs`, (_req, res, ctx) =>
res(ctx.status(200), ctx.json(quickFiltersListResponse)),
),
rest.put(`${ENVIRONMENT.baseURL}/api/v1/orgs/me/filters`, async (req, res, ctx) => {
// capture payload if needed
return res(ctx.status(200), ctx.json({}));
}),
);
Mock hooks minimally at module level:
jest.mock('hooks/queryBuilder/useQueryBuilder', () => ({
useQueryBuilder: jest.fn(),
}));
Interact via accessible roles:
const user = userEvent.setup({ pointerEventsCheck: 0 });
await user.click(screen.getByRole('button', { name: /save changes/i }));
expect(screen.getByText(/ADDED FILTERS/i)).toBeInTheDocument();
Virtualized scroll:
const scroller = container.querySelector('[data-test-id="virtuoso-scroller"]') as HTMLElement;
scroller.scrollTop = 500;
fireEvent.scroll(scroller);
Routing-dependent behavior:
render(<Page />, undefined, { initialRoute: '/logs-explorer?panelType=list' });
// Pattern params: mount under the route the page reads them from.
render(<Page />, undefined, {
initialRoute: '/dashboard/abc',
routePath: ROUTES.DASHBOARD,
});
// Where the component navigated to.
expect(getCurrentLocation().pathname).toBe(ROUTES.HOME);
Never mock the router packages (react-router, react-router-dom) or lib/history;
signoz/no-direct-react-router-import rejects it. When a test cannot render at a route,
or asserts the call itself, spy on the lib/router facade with tests/router-mocks:
mockAppLocation({ pathname: ROUTES.LOGS_EXPLORER });
mockAppParams({ dashboardId: 'abc' });
const navigate = mockAppNavigate(); // what useAppNavigate() returns
const navigateSpy = mockNavigate(); // module-level navigate()
Notes
- Global mocks configured in Jest:
uplot→__mocks__/uplotMock.ts. - If a test needs custom behavior (e.g., different API response), override with
server.use(...)locally.