Skip to content

Add component smoke tests for public library exports #11

Description

@alx-so

Problem

The package exposes Input, InputSelect, and Select, but there are no tests proving that the public exports render with minimal supported props or respect basic public contracts.

This should be added before fixing the runtime bugs so later changes have a baseline component safety net.

Impact

Without component smoke coverage, a fix can accidentally break public exports, required props, or core render paths while still passing pure utility tests.

Code references

  • src/index.tsx#L1-L5: public package exports.
  • src/components/Input/Input.tsx#L213-L236: Input render path.
  • src/components/Select/Select.tsx#L225-L248: Select render path.
  • src/components/InputSelect/InputSelect.tsx#L222-L237: InputSelect render path.
  • package.json#L106-L111: Jest uses the React Native preset.

Acceptance criteria

  • Tests verify Input, Select, and InputSelect render with minimal valid props.
  • Tests verify public exports from src/index.tsx are importable.
  • Tests include at least one multi-select render path with tags.
  • Tests do not start Expo, Metro, a browser, or any long-running server.
  • If a new component testing dependency is needed, open a dependency decision before implementation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: apiPublic API, props, and exportsarea: controlled-stateControlled and uncontrolled component statearea: inputInput and TextInput behaviorarea: multiselectMultiple selection and tag behaviorarea: testsAutomated test coverage and test configurationenhancementNew feature or requestpriority: criticalMust fix before the next releasetype: testingTest infrastructure and coverage work

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions