Added unit testcases for contentstack seed plugin

[sunil-lakshman]

No description provided.

[Copilot]

Pull Request Overview

This PR adds comprehensive unit test coverage for the contentstack seed plugin. The changes modernize the test suite by replacing dependency on external config files with mocked implementations, while improving the overall test configuration and tooling.

Reviewed Changes

Copilot reviewed 11 out of 13 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/contentstack-seed/tests/seeder.test.ts	Complete rewrite replacing actual client testing with mock-based unit tests for ContentModelSeeder functionality
packages/contentstack-seed/tests/interactive.test.ts	Updated to remove config file dependency and improve TypeScript type safety
packages/contentstack-seed/tests/importer.test.ts	Replaced integration-style tests with focused unit tests using mocks for path handling and command execution
packages/contentstack-seed/tests/github.test.ts	Converted from integration tests with axios to pure unit tests with mock implementations
packages/contentstack-seed/tests/contentstack.test.ts	Complete rewrite to test ContentstackClient with proper mocking of the management SDK
packages/contentstack-seed/package.json	Added TypeScript ESLint dependencies and updated test scripts
packages/contentstack-seed/jest.config.js	Enhanced Jest configuration with better TypeScript support and module handling
packages/contentstack-seed/.eslintrc	Modernized ESLint configuration with TypeScript support
packages/contentstack-seed/tsconfig.json	Added TypeScript compiler options for better module resolution
.github/workflows/unit-test.yml	Added CI workflow step to run contentstack-seed tests
.talismanrc	Updated checksums for modified files

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (6)

packages/contentstack-seed/tests/seeder.test.ts:100

• This assertion is checking a resolved value but not awaiting the promise. Use await expect(contentTypeCount).resolves.toBe(0) or expect(await contentTypeCount).toBe(0) for proper async testing.

    expect(contentTypeCount).resolves.toBe(0);

packages/contentstack-seed/tests/seeder.test.ts:112

• This assertion is checking a resolved value but not awaiting the promise. Use await expect(userConfirmation).resolves.toBe(false) or expect(await userConfirmation).toBe(false) for proper async testing.

    expect(userConfirmation).resolves.toBe(false);

packages/contentstack-seed/tests/seeder.test.ts:137

• This assertion is checking a resolved value but not awaiting the promise. Use await expect(organizations).resolves.toEqual([]) or expect(await organizations).toEqual([]) for proper async testing.

    expect(organizations).resolves.toEqual([]);

packages/contentstack-seed/tests/seeder.test.ts:2

• This test creates a mock function but doesn't test the actual ContentModelSeeder class. Consider testing the real parsePath method or moving this to a dedicated GitHub client test file.

  test('should parse GitHub path correctly', () => {

packages/contentstack-seed/tests/github.test.ts:4

• This test implements the logic inline rather than testing the actual GitHubClient.parsePath method. Consider importing and testing the real implementation.

    const parsePath = (path: string) => {

packages/contentstack-seed/tests/importer.test.ts:4

• This test only verifies mock function calls without testing actual importer functionality. Consider testing the real path construction logic from the importer module.

  test('should construct import path correctly', () => {