Bug fixes

Changes in version 1.1.3

• Improved handling of configuration file changes.

This change should resolve the following issue:

• Tests "disappear" after changing config files.

Bug fixes

• Improved "discovery" of node.exe and npm.cmd paths.

This change should resolve the following issue:

• Test Adapter error - "Could not start Karma".

Traits

Changes in version 1.1.1

• A trait specified as a string or with only a name will be shown in the Test Explorer as just the string or name.
• Traits with only a value are ignored

Extensions and traits

Changes in version 1.1.0

• The name of the outermost suite is now used as the class name for a test. This can be customized using new properties Name and Extensions in KarmaTestAdapter.json.
• The display name of each test now includes the suites separated by a space. This can be customized using new properties Name and Extensions in KarmaTestAdapter.json.
• New properties in KarmaTestAdapter.json:
  • Name The name of the test container. Used in the default generation of the fully qualified name for each test.
  • Traits An array of traits to be attached to each test. A trait can be a string or an object containing properties Name and Value. For traits specified by a string the string is the trait value and the trait name is "Category".
  • Extensions Path to a node.js module implementing extensions.
• Logging to the output window is significantly less chatty.
• The code in the Karma Test Adapter has been refactored to enable sharing code with other test adapters. A lot of the code has moved to JsTestAdapter, which can be install as a NuGet package.

These changes resolve the following issues:

• Concatenate a test's suites in front of the test description.
• configure test entries so that they behave as expected in Test Explorer's grouping and sorting.

Bug fixes

Changes in version 1.0.3

Bug fixes

• Fixed: The adapter does not work if both karma-jasmine and karma-jasmine-matchers are used .

Read KarmaTestAdapter.json as unicode with or without BOM

Changes in version 1.0.2

Bug fixes

• Fixed: Can not read KarmaTestAdapter.json if it is encoded with a BOM.

  From now on KarmaTestAdapter.json must be encoded in one of the following encodings:

  • UTF-8
  • UTF-8 with BOM / Signature
  • UTF-16 Big-Endian with BOM / Signature
  • UTF-16 Little-Endian with BOM / Signature

Test containers

Changes in version 1.0.1

Improved identification of test containers:

• Test containers specify which Karma configuration files to use when running tests.
• A project can contain more than one test container.
• A directory can contain at most one test container.
• Test containers are files named karma.conf.js or KarmaTestAdapter.json.
• If a test container is named karma.conf.js it specifies itself as the Karma configuration file to use.
• If a test container is named KarmaTestAdapter.json it specifies the Karma configuration file to use in the optional KarmaConfigFile setting. If the KarmaConfigFile setting is not specified, then karma.conf.js in the same directory is used.
• A test container, which specifies a Karma configuration file that is not included in a project in the current solution or does not exist, will be disabled. I.e. no tests will be run for the container.
• Only test containers, that are included in a project in the current solution, are used.
• If there is a KarmaTestAdapter.json file in a project, then any karma.conf.js file in the same directory is not used as a test container.
• If there is a KarmaTestAdapter.json in a project in the current solution, that specifies a Karma configuration file in a different directory or project, then that Karma configuration file is not used as a test container.

Bug fixes

• Fixed: The adapter does not work with karma configuration files not called karma.conf.js.
• Fixed: The format of the URI could not be determined.
• The adapter now works with globally installed modules

A complete rewrite of the Karma Test Adapter

Some of the major changes in version 1.0.0

• The node package karma-vs-reporter is deprecated, and is no longer used
• The settings file karma-vs-reporter.json is now KarmaTestAdapter.json
• Karma is now always run in the background, and the settings ServerMode and ServerPort are no longer used.
• Deciding when to run tests is now left up to Karma. The adapter only watches configuration files.
• Test results are shown in the Test Explorer as soon as Karma has completed a test run.

Bug fixes

Changes in version 0.8.3

• Ignore tests with no names

Bug fixes

Changes in version 0.8.2

• Bug fixes