Angular2组件单元测试批量隔离执行方案咨询（UI变更场景）

Got it, let's tackle this problem—dealing with a flood of failing tests after a big UI revamp is no fun, and manually tagging every test file with fdescribe/fit sounds like a total drag. Here are some clean, non-intrusive ways to run tests only for your target folders, so you can validate your updated components without wading through all the old failing tests:

For Jest (Most Common React/JS Test Framework) #

• Command-line path targeting: Run tests directly for a specific folder by passing the path pattern to Jest. For example:

  jest src/components/your-updated-folder/**/*.test.js
  

  The ** wildcard matches all subfolders, so this will run every test file ending with .test.js inside your target folder and its subdirectories.
• Temporary config overrides: If you want to reuse the same target across multiple runs, you can tweak your Jest config temporarily:
  • Create a temporary config file (e.g., jest.temp.config.js) with:

    module.exports = {
      // Reuse your base config here
      ...require('./jest.config.js'),
      testMatch: ['**/src/components/your-updated-folder/**/*.test.js']
    };
    

  • Run tests with this config:

    jest --config jest.temp.config.js
    

  • Alternatively, ignore all non-target folders with testPathIgnorePatterns:

    testPathIgnorePatterns: ['<rootDir>/src/components/old-ui-folders/']
    

For Mocha #

If you're using Mocha instead, similar path-based targeting works:

• Command-line path pattern:

  mocha src/components/your-updated-folder/**/*.test.js
  

• Temporary config adjustments: Add a path filter to your .mocharc.json or use the --grep flag if you've named your test files consistently (though path targeting is more straightforward here).

Bonus: Flexible npm Script #

To make this even easier, add a script to your package.json so you don't have to type the full path every time:

{
  "scripts": {
    "test:specific": "jest $TEST_FOLDER"
  }
}

Then run it with:

TEST_FOLDER=src/components/your-updated-folder/**/*.test.js npm run test:specific

All these methods let you focus on validating your updated UI components without modifying any test code—no more manual fdescribe/xit changes across dozens of files.

内容的提问来源于stack exchange，提问作者Karthik