Instead of duplicating all your app's Javascript references in your Karma config, just refer to your HTML files, test files and mocks.
Also supports reading external Javascript files via HTTP.
This preprocessor lets you load your project's HTML files, from which the files denoted by the src
field in the <script>
files are read or downloaded and included in the test suites.
This is handy for running your tests againts your dist package.
Pros:
- Your project's html files are used, meaning you are guaranteed that there is consistency between test and live resources
- You do not need to manage local copies of resources using, e.g. bower
Cons for case 2:
- Tests require Internet connectivity
- Downloads on each test iteration
$ npm install karma-preprocessor-pullscripts
First, include html files in the files
section of your karma.conf.js
. These will be processed in order.
files: [
'./path/to/file1.html',
'./path/to/file2.html',
Add pullscripts
to your preprocessor list:
preprocessors: {
'./path/to/*.html': 'pullscripts',
},
Configure the file prefix:
pullscripts: {
// Prefix referenced local file names with this before reading them up.
filePrefix: 'dist/'
},
All scripts are processed in order of appearance in the HTML files. For example if jquery
is included before angular
, then the jquery script will be downloaded and included before the angular script. If you have multiple html files with different scripts included, you might need to ensure the load order (order in files
array) is consistent.
BSD