Running tests in both headless and browser - yeoman

I'd like to run my tests in PhantomJS using yeoman test as well as in browser using yeoman server:test. The problem though is that PhantomJS doesn't find my includes in my index.html:
<script src="scripts/view/customer_view.js"></script>
...because it looks inside the test/-directory. Of course it would work if I tell my coffee-task to duplicate all the files into the test/-directory as well. But that seems wrong.
So, is there any way to use:
the same include paths for headless and browser?
the same files that have already been created in /temp/scripts? (because I use CoffeeScript)


After digging deeper on GitHub, I found out that I have to replace the URI in the Gruntfile.js:
// headless testing through PhantomJS
// mocha: {
jasmine: {
// all: ["test/**/*.html"]
all: ["http://localhost:3501/index.html"]
}
Note
As of Yeoman 0.9.6 it's also required to modify the grunt task:
// Alias the `test` task to run the `jasmine` task instead
// grunt.registerTask("test", "jasmine");
grunt.registerTask("test", "server:phantom jasmine");

Related

In Fitnesse I am getting an error when I try to run tests but my coworkers are able to run tests on the same scripts with no problem

Here's what some of it looks like:
script com.appiancorp.ps.automatedtest.fixture.SitesFixture Could not invoke constructor for com.appiancorp.ps.automatedtest.fixture.SitesFixture[0]
setup with The instance scriptTableActor.setupWithBrowser. does not exist CHROME browser
set appian version to The instance scriptTableActor.setAppianVersionTo. does not exist 19.4
set appian locale to The instance scriptTableActor.setAppianLocaleTo. does not exist
I do have Chrome installed and chrome driver and I opened fitnesse through chrome.

Obviously, the problem is that you don't have Chrome installed.

ERROR: need to include some adapter that implements __karma__.start method [duplicate]

I'm trying to add some unit tests to one of my projects.
So far I've installed and configured karma, and have installed jasmine. I've one test file in my test/ folder.
The karma server has started, the browser page is ready, but karma run fails as follows:
$ karma run karma-conf.js
[2014-06-14 15:19:11.046] [DEBUG] config - Loading config /foo/test/karma-conf.js
Waiting for previous execution...
Chrome 35.0.1916 (Linux) ERROR
You need to include some adapter that implements __karma__.start method!
This error message doesn't Google well.
Is this something obvious, or do I need to provide more information?

It does seem like this is a very general error, however in my case the problem was either that I didn't run karma start from the correct folder, or that I didn't restart it after changing the configuration.
I'll leave this question open and hopefully it can become a resource for others who experience this error message.

If you name your karma config file karma.conf.js, you can simply type karma start.
Otherwise specify the filename karma start karmafile.js
(I was in the right directory, but was not specifying a file name.)

You need to run your karma run or whatever function in the folder where karma-conf.js is in.

In my case I had to rename the file to karma.conf.js then do karma start

I had a problem with karma.conf.js file code format:
files: [
// Modules
,"client/bower_components/angular/angular.min.js"
,"client/bower_components/angular-mocks/angular-mocks.js"
// App
,"client/app/app.module.js"
// Test
// ,"test/**/*.spec.js"
],
The extra comma in files array have cause this error:
You need to include some adapter that implements __karma__.start method!

I was not running karma start command from the path where my karma.conf.js was. I switched to that folder and ran the same command. Thats all

I was facing this issue while running specs on the Angular.js codebase. I had to run npm install karma-jasmine -g to get this working.

If you typing "karma start", you must have a karma.conf.js file in the current folder. or just "karma start /path/karma.conf.js"
Try to create a new karmar.conf.js by "karma init /path/karma.conf.js"

In my case, I was applying by mistake the commonjs preprocessor to the karma-* modules and the adapter.js from karma-chrome and karma-firefox was broken this way.
Unfortunately, this is a very generic error.

I was getting the same error because the project was using Babel 6 and I had forgotten to add the babelrc file. Just sharing in case this could help.

In my case, the message was in fact very descriptive: I forgot to add an adapter, in my case Jasmine, into the config file. Thus:
module.exports = function(config) {
config.set({
browsers: ['Chrome'],
singleRun: true,
frameworks: ['jasmine'],
files: [
// ... files ...
],
// other configs
});
};

You need to configure your "my.conf.js" file, because it contains all the info to use to test your code.
All what you need to write is this:
The configuration file can be generated using karma init:
$ karma init my.conf.js
Which testing framework do you want to use?
Press tab to list possible options. Enter to move to the next question.
jasmine
Do you want to use Require.js?
This will add Require.js plugin.
Press tab to list possible options. Enter to move to the next question.
no
Do you want to capture a browser automatically?
Press tab to list possible options. Enter empty string to move to the next question.
Chrome
What is the location of your source and test files?
You can use glob patterns, eg. "js/*.js" or "test/**/*Spec.js".
Press Enter to move to the next question.
*.js
test/**/*.js
Should any of the files included by the previous patterns be excluded?
You can use glob patterns, eg. "**/*.swp".
Press Enter to move to the next question.
Do you want Karma to watch all the files and run the tests on change?
Press tab to list possible options.
yes
Config file generated at "/Users/vojta/Code/karma/my.conf.js".

You must specify the karma configuration file to karma.
karma start karma.config.js
It works for me

I must add that in my case karma was giving me the error because I had [square] brackets in the name of one of the parent folders.

Tt's complaining about the adapter which is probably jasmine or mocha.
Either the adapter is missing, either is not setup correctly, either it's an outdated or buggy version of the adapter.
In my case I had an old version of mocha 2.5.3 which was not compatible with karma 1+.
I updated the mocha dependency to the latest version available 3.2.0 and the problem solved.

While working on numerous vaguely described errors, I tried setting basePath: '../', After correcting other errors (like missing commas that were described as object content errors) the last change back to basePath: '', got karma to work. karma's error statements need a lot of work. It is not simple to get it going.

I had the same issue. My browser would open but on my terminal it threw the following error
30 08 2017 11:19:28.272:INFO [Chrome 58.0.3029 (Linux 0.0.0)]: Connected `enter code here`on socket 5sSs6E5KmpUVRp6LAAAB with id 93886631
Chrome 58.0.3029 (Linux 0.0.0) ERRORSome of your tests did a full page reload!
I checked my karma.conf.js file. In the framework array , i had included jasmine and requirejs. But i had only installed karma-jasmine.Removing requireJS and rerunning the karma start worked!

I've been struggling with this too. What I came up to is that this error occurs because one of the following reasons
No test adapter installed or defined (frameworks property in karma.conf.js
No karma configuration found (ie, no karma.conf.js in current dir or no config file specified in command)
My problem was that my config file was named karma.config.js instead of karma.conf.js.
If you've installed the test adapter but it still doesn't work, try running karma init and go through the guided config setup.

You will have to specify the directory of karma.config.js when you run start karma.
Try
karma start karma.config.js

I had a bad 'files' configuration in my karma.conf.js
files: ['**/*.js'],
this caught up all the files in node_modules/ including those of the karma-jasmine plugin, as it was seen as sourde files it wasn't loaded on startup. Changing to
files: [
'src/*.js',
'spec/*.js'
],
solved the problem in my case

FWIW - sourcing the file path of karma.conf.js worked for me locally, but not on my jenkins builder. I have zero clue why this is the case, but on jenkins it was throwing this error unless the karma.conf.js file was in the root directory where the karma command was given. I'm using rails and running the js specs through a rake task. Code is below which might be helpful for some.
https://gist.github.com/daino3/a39486ff8bfc1668e923

The issue in my case was that karma didn't pick up any files. Fixing it in karma.conf.js solved the issue.

Same issue happened to me, and it was due to an outdated module.
Running npm update solved it.

In my case, it was not karma-related at all! I run karma from gulp, with ES6/babel, and there was actually a code syntax error, flagged by a babel error above my karma:
ERROR [preprocessor.babel]: xxx.js: Unexpected token (19:83)
I fixed that in my src and karma was happy again.

In my case, the configuration file name was different. So, running the command specifying the conf file solved my issue.
>> karma start unit-tests.conf.js
No captured browser, open http://localhost:9876/
...
And for 'PhantomJS', opening the link specified(localhost:9876) in the browser executes the test cases.
Hope it helps. :)
EDIT 1: My Karma Config File
module.exports = function(config) {
config.set({
// base path that will be used to resolve all patterns (eg. files, exclude)
basePath: '',
// frameworks to use
// available frameworks: https://npmjs.org/browse/keyword/karma-adapter
frameworks: ['jasmine'],
// list of files / patterns to load in the browser
files: [
'./node_modules/angular/angular.js',
'./node_modules/angular-ui-router/release/angular-ui-router.js',
'./node_modules/angular-mocks/angular-mocks.js',
'./app/services/users/users.js',
'./app/app.js',
'./app/services/users/users.spec.js'
],
// list of files to exclude
exclude: [
],
// preprocess matching files before serving them to the browser
// available preprocessors: https://npmjs.org/browse/keyword/karma-preprocessor
preprocessors: {
},
// test results reporter to use
// possible values: 'dots', 'progress'
// available reporters: https://npmjs.org/browse/keyword/karma-reporter
reporters: ['spec'],
// web server port
port: 9876,
// enable / disable colors in the output (reporters and logs)
colors: true,
// level of logging
// possible values: config.LOG_DISABLE || config.LOG_ERROR || config.LOG_WARN || config.LOG_INFO || config.LOG_DEBUG
logLevel: config.LOG_INFO,
// enable / disable watching file and executing tests whenever any file changes
autoWatch: true,
// start these browsers
// available browser launchers: https://npmjs.org/browse/keyword/karma-launcher
browsers: ['Chrome'],
// Continuous Integration mode
// if true, Karma captures browsers, runs the tests and exits
singleRun: false,
// Concurrency level
// how many browser should be started simultaneous
concurrency: Infinity
})
}

I received this error because I required the same dependency twice!
Removing the duplicate file dependency removed the error for me. Circled in blue below.

Given this is the first result on google for this error message, I figured I'd mention my resolution here.
I was getting this error after converting an AngularJS 1.8 project to Typescript and trying to change over my Karma tests to use the typescript preprocessor.
I finally realized that adding import angular from 'angular' resolved the issue on Karma's side, but then angular turned up as undefined in webpack's build.
Eventually thanks to this answer on a question about that error message, I updated my import statements to import * as angular from 'angular', and finally it worked! (Ultimately I had to resolve every compilation error on every typescript file for complete resolution, which I had been somewhat ignoring since the webpack build worked.)
Hopefully this can help someone with this problem!

I had the same problem but above mentioned solutions didn't work for me. What I eventually found out is that my karmaWebpackConfig was using "babel-loader" as loader. I just removed that line and it worked for me.

How to debug browser tests with the new test package

browser tests need to be run from command line like pub run test -pdartium. Is there a way to debug such tests.

The Dart team is working hard to make tests with the new test package debuggable. Until the related issues are fixed you can use this workaround:
To run browser tests with the new test package, for example from WebStrom, including debugging, just replace the <x-test-dart ...> tag with a normal Dart script tag pointing to your test file and run it like any Dart browser application from WebStorm.
This also works for Polymer tests. Ensure you run await initPolymer(); or the appropriate initialization necessary for the used Polymer version.
I usually create a copy of the test entry page file where I can keep the replaced script tag.

pub run test -pdartium --pause-after-load
starts the test only after I click a "play" button on the test page. This gives me time to open up Dev Tools in Dartium and set breakpoints. I can also open up the Observatory and do stuff there.

Is there a way to get JUnit code coverage when running in the browser?

We are currently working on getting better code coverage for one of our JS libraries. I have the The Intern up and running, and can run tests in the browser. However, our libraries create DOM elements in some of their functions, making it so we can't run JUnit from the terminal because Node.js doesn't allow for DOM construction in tests. Is there a way we can get JUnit code coverage on the html and console output we get when we run The Intern in the browser?

I found the answer. From this link: https://theintern.github.io/intern/#local-selenium
Using ChromeDriver (Chrome-only)
If you’re just looking to have a local environment for developing functional tests, a stand-alone ChromeDriver installation works great.
1. Download the latest version of ChromeDriver
2. Set tunnel to 'NullTunnel'
3. Run chromedriver --port=4444 --url-base=wd/hub
4. Set your environments capabilities to [ { browserName: 'chrome' } ]
5. Run the test runner
Once you have that setup and running, you can run
node_modules/intern/bin/intern-runner.js config=tests/intern reporters=JUnit filename=junit.xml
This will allow the tests to run in a chrome instance, and then output the results to a report that can then be upload somewhere.

How to generate results after selenium test in Ruby?

I have recently started using ruby to write tests for selenium but I would like a way for the tests to be exported into a results file.
For an example of what i mean. I was exporting the tests from the IDE to html and then running them using
java -jar selenium-server-standalone-2.39.0.jar -htmlSuite *firefox http://google.com /path/to/suite.html /path/to/results.html
in the command line and it would run the suite.html and then post the results in results.html
Is this possible in Ruby?

Looks like someone has already taken on the same challenge before. See this article how to export results when running selenium ruby webdriver scripts to output files from command prompt ruby window.
You may have to write up a rake file, but I believe it will be a good experience that will make you better acquainted with ruby and how to go about selenium testing with it.

Resources