I am looking to test a scenario where the application blocks the user to proceed edge browser and displays a message that the application is unsupported on edge.
I am unsure if we can exclude test suite on various browsers and make it run only on chrome ?
You can tell protractor which tests should run on each browser by adding a specs property to each browser in the multiCapabilities section. If multiCapabilities is specified then the capabilities property will be ignored.
multiCapabilities: [{
browserName: 'chrome',
specs: ['spec/chromeOnlySpec.js', 'spec/chromeOnlySpec2.js']
}, {
browserName: 'MicrosoftEdge',
specs: ['spec/runsOnEdgeSpec.js', 'spec/runsOnEdge2Spec.js']
}]
Related
I'm struggling with setting up environment for old tech project with PHP5.
My OS is Windows and I have installed so far VSCode plugins: PHP Debug, PHP Intelephense, PHPUnit, PHPUnit Test Explorer.
I downloaded phpunit-5.7.27.phar and configured VSCode according to documentation.
Settings.json
{
"php.validate.executablePath": "C:/wamp64/bin/php/php5.6.40/php.exe",
"phpunit.phpunit": "C:/wamp64/bin/php/php5.6.40/phpunit-5.7.27.phar",
"phpunit.php": "C:/wamp64/bin/php/php5.6.40/php.exe",
"intelephense.environment.phpVersion": "5.6.40",
"intelephense.environment.includePaths": [
"C:/wamp64/bin/php/php5.6.40/phpunit-5.7.27.phar",
"C:/wamp64/bin/php/php5.6.40/php.exe",
"C:/wamp64/bin/php/php5.6.40/"
]
}
Launch.json
{
"version": "0.2.0",
"configurations": [
{
"name": "Listen for XDebug",
"type": "php",
"request": "launch",
"port": 9000,
"xdebugSettings": {
"max_children": 256,
"max_data": 500,
"max_depth": 3
}
},
]
}
What works for me fine is breakpointing on running app with xdebug and running unittests with Cmd+Shift+P.
What I need help with are as follows:
Code editor shows error for PHP unit classes and methods (even though unittests are executing fine as is). Do I need to add to path something besides phar file? Is VSCode non-compatible with phar files? The same happens for PHPUnit\Framework\TestCase.
I can't figure out how to configure Test Explorer plugin to show nicely tests tree. Does it require some configuration in Launch.json? Launching tests with Cmd+Shift+P displays results only in terminal.
PHP Intelephense requires installed PHPUnit with composer in workspace.
composer require --dev phpunit/phpunit
PHPUnit Test Explorer has by default Phpunit: Files setting set to {test,tests}/**/*Test.php, so changing it to proper glob should allow plugin to detect all tests.
Should Karma launch a browser that with my front-end app loaded?
I should see a landing page of my app if Karma is correctly loaded, is this correct?
If not loading my app landing page, why Karma launch a visible browser?
This is my karma.config.js
I am learning Karma, not sure if I did everything alright.
var webpackConfig = require('./webpack.config.js');
webpackConfig.entry = {};
/*
The entry point from the referenced Webpack configuration
has to be removed or tests will fail in weird and inscrutable
ways. Easy enough, just define an empty entry object.
*/
module.exports = function(config) {
config.set({
bathPath: './dist/',
webpack: webpackConfig,
/* reference the Webpack configuration in the Karma configuration */
preprocessors: {
// './dist/bundle.js': ['webpack'],
'./test/*.js': ['webpack']
/* application’s entry point, karama-webpack plugin requires this */
/* you have to tell Karma that you want the karma-webpack plugin
to process these files. That’s what ['webpack'] does.
*/
},
/*
The plugins section is missing from my karma.config.js file.
When missing, Karma will load any plugins it can find in the
node-modules folder. Much simpler in my opinion.
*/
frameworks: ['jasmine'],
files: [ {pattern: 'index.html', }, './test/*.js'],
/* The files array determines which files are included in the
browser and which files are watched and served by Karma
*/
browsers: ['Chrome'],
reporters: ['progress'],
port: 9876
});
};
This is correct. Karma loads a page which includes all your javascript and all your specs. It then runs any specs that might be in there. This is not full integration testing. This is javascript unit testing.
If you wanted to debug in browser, you can click the debug button and you'll see the page that it runs. Hit that page and check out the console and you'll see your spec output.
You'll need something more for full integration tests like protractor or capybara or ...
Probably depends on what you're using to build your site.
I have typescript code and typescript jasmine tests running within Karma. I can run the tests from the command-line (using Karma), and also run the tests from the ReSharper test runner. Presumably I could also run the tests using Karma Test Adapter VS extension or VS Adapter for Karma. So, lots of options for running the tests.
My question is: How do I debug the tests, in the VS debugger?
I was able to get Visual Studio debugging of typescript jasmine tests, running in Karma, working. Wow, that's a mouthful.
Here's how I did it:
In IE, Options, Advanced: Clear the "Disable script debugging (Internet Explorer)" checkbox.
Install the node modules (globally) required to run karma - if you haven't already:
npm install -g karma karma-chrome-launcher karma-ie-launcher jasmine-core karma-jasmine karma-jasmine-html-reporter
npm install -g phantomjs karma-phantomjs-launcher
In the karma.conf.js, add support for serving the required sourcemap and typescript files. Here's mine:
module.exports = function(config) {
config.set({
frameworks: ['jasmine'],
files: [
'bower_components/angular/angular.js',
'bower_components/angular-mocks/angular-mocks.js',
'dist/**/*.js',
'test/out/**/*.js',
// Key addition to support debugging typescript tests
// Enable serving (but don't include as scripts) sourcemap and typescript files
{pattern: '**/*.js.map', included: false},
{pattern: '**/*.ts', included: false}
],
reporters: ['html', 'progress'],
port: 9876,
colors: true,
logLevel: config.LOG_INFO,
autoWatch: true,
browsers: ['PhantomJS']
});
}
After compiling your typescript, run karma, launching IE:
karma start --browsers=IE --reporters=html
In Visual Studio, Debug menu | Attach to Process... , then choose the iexplore.exe instance(s) that look right - eg the title may match the Karma web page title ("Karma DEBUG RUNNER" currently), and the process Type must be "Script". If typescript debugging doesn't work, try adding multiple iexplore.exe instances, including all the probably Script instances.
After that, you should see a "Script Documents" folder in Solution Explorer, and you should be able to put breakpoints in your typescript, run the tests in your browser, and step through your typescript code.
It turns out that all these steps also work for debugging Typescript tests and code in Chrome - just change step 4 to:
karma start --browsers=Chrome --reporters=html
(skip step 5) then open Chrome developer tools to debug the typescript in chrome.
We're running Protractor with Selenium Grid, with (for now) 2 browsers. When tests fail I see that they fail, and I see how many tests fail on each browser but somehow I cannot see on which browser the tests fail.
Is this a Selenium or a Protractor shortcoming or am I doing something wrong?
Do you use jasmine reporters? I find the console indicates clear enough in which browser the error originates. And of course the html report is very clear.
Add these in the protractor.conf.js in the onprepare block like this.
onPrepare: function () {
// The require statement must be down here, since jasmine-reporters
// needs jasmine to be in the global and protractor does not guarantee
// this until inside the onPrepare function.
require('jasmine-reporters');
jasmine.getEnv().addReporter(new jasmine.ConsoleReporter());
jasmine.getEnv().addReporter(new HtmlReporter({
baseDirectory: 'reports/screenshots' ,
takeScreenShotsOnlyForFailedSpecs: true
}));
},
Be sure to use jasmine-reporters ~0.4.0 ,the 1.0.0 does not work yet with protractor because it work with a newer jasmine version then protractor until now uses.
I have got a set of test that run fine on chrome but when I change the capabilities browserName from chrome to firefox don't even get a error info
//Before
capabilities: {
'browserName': 'chrome',
'chromeOptions': { args: ['--test-type', 'show-fps-counter=true'] }
},
//After
capabilities: {
'browserName': 'firefox'
},
I found the problem with firefox, basically my protractor config was not using any webdriver server setting but was using the default server, this way was quite handy since did not have start selenium by my self
In order to fix this issue I am starting selenium server by myself spesifiying firefox and chrome drivers
java -jar "C:\Users\%USERNAME%\AppData\Roaming\npm\node_modules\protractor\selenium\selenium-server-standalone-2.42.1.jar" -Dwebdriver.chrome.driver="C:\Users\%USERNAME%\AppData\Roaming\npm\node_modules\protractor\selenium\chromedriver.exe" -Dwebdriver.firefox.bin="C:\Users\%USERNAME%\AppData\Local\Mozilla Firefox\firefox.exe"
It seems that firefox 35,36 is not supported by protractor so one workaround is to download firefox 34 here and set its path by adding
"firefox_binary": "path/to/custom/firefox"
"binary_": "path/to/custom/firefox"
in your conf file as stated here by #6220119