I have a problem with Behat, if I run a new test, it does not print the regular expressions. Is there a solution to this problem ? I googled it but I did not find an answer.
Note: I installed Behat using the git method. I think this might have something to do with it because it installed differently then the composer method (it put the files in a Behat folder and it installed some default tests). Yesterday I used the composer method and everything worked fine.
Related
I'm trying to run the Kotlin/Native Hello Program
but the terminal says the command kotlin-native cannot be found. I'm on a MacBook, using zsh (get same error when I use bash) and installed Kotlin via Homebrew before, so kotlin and it's compiler works on my machine, the kotlinc command works just fine. I'm trying to use the compiler instead of gradle for now. Is there a different command I'm supposed to be using?
It sound like you may have had a similar problem to me. Installing kotlin-native via homebrew did not install the kotlinc-native command.
To get the command working, I had to do the following:
Go to https://github.com/JetBrains/kotlin/releases and get the latest version of Kotlin
Extract it to .kotlin in the home directory
Add export PATH="$HOME/.kotlin/bin:$PATH" to .zshrc
The problem with this method is that it's completely disconnected from Homebrew. You will have to run the steps again every time you want to update Kotlin.
You've typed kotlin-native but the tutorial says kotlinc-native, which is the actual name of the process file.
If kotlinc works then you might just have a typeo.
I don't use these processes directly, but I'm somewhat familiar with them. My guess is check the name.
We have currently about 200 test features. We start to face something strange, most of the times tests are just stuck and would not proceed when we run mvn test command as the following:
mvn clean test -Dcucumber.options="--tags $tags" -Dtest=TestRunner -Dkarate.env=$env
Some tests would run as it was perfectly fine. But at some point the rest will just stuck as it it hangs.
We run the tests in parallel using 10 threads.
It stucks like this
Anybody experienced similar things? Any ideas what could possibly went wrong?
Thanks
This should be fixed in 0.9.5.RC3 - it is stable to use for API testing, so I recommend you upgrade.
If anyone faces this problem for any other version of Karate, please understand that the best (and possibly only) way to troubleshoot or solve this - is to follow this process: https://github.com/karatelabs/karate/wiki/How-to-Submit-an-Issue
I actually have the same problem as you but I can't comment because of reputation, my project works with Gradle and I'm using IntelliJ IDEA and JDK1.8(at another moment before all this I tried Jetbrains SDK11 but had the same problem, I downgraded to java 8 and everything worked again) on this ocassion I did as peter said and upgraded to 0.9.5.RC4 but still when I execute some of my features they never end, for example, I'm currently working on a very simple feature that calls another feature for login, it works for many other features but for this one it appears to get to the end of its execution and never go back to the caller feature, as I was running out of options I made a new simple project copied the resources folder I store my features in and my run parallel class and tried again but it behaves in the same way, the execution never ends.
I'll upload an image with my screen while it executes as you can see it's been executing for 15 minutes
projectView
Installing PHPUnit with composer globally seems more convenient to me for those two reasons:
1. Using it everywhere without needing an extra install.
2. Just running phpunitinstead of vendor/bin/phpunit (using an alias might solve this)
Are there any reasons why a local install might be the better choice? For example: using the exact same versions every time. (don't have a lot of experience with PHPUnit, so not sure if this really is an issue or not)
The big disadvantage of installing packages globally is that you might end up with different versions of PHPUnit between developers in your team (unless you are the only developer). This might cause some side effects.
If you install it locally using composer.json, then every developer in your team will have exactly the same version as you do for that specific application. Also, everybody will see when you change the version in composer.json.
If you don't like typing vendor/bin/phpunit, you can use Makefile (which is also in your project):
test:
vendor/bin/phpunit --configuration=test/Unit/phpunit.xml
then run it ...
make test
I like to install it via composer and the require-dev block, but another way that does come highly recommended is to download the phpunit.phar into the project, to use that.
Either way, you control exactly which version is being used (and when it's updated) - which is the most important part, as you can't so easily control what people have installed globally.
I'm stumped. I cannot understand the getbootstrap.com Getting Started info. I'm running on Windows 7 Pro. I would like to use Pingendo - which I'm new to - to create my website.
I downloaded the distribution version bootstrap-3.3.7-dist.zip (pre-compiled) and unzipped it. Then I came to the MaxCDN code. Where do I put that code??
For the source code version, I see references to things I don't know about: Bower, npm, Composer, Grunt, Less, and SASS. All these appear to be Linux based tools - from the command lines shown. How does one accomplish the same thing under Windows without installing yet more tools? Do I even need to compile this code to use the greater features?
You can either add the downloaded bootstrap css and js files to your project and reference them or you can just use the cdn which is just the same files hosted on a server. You do now have to know about any of those to get started with Bootstrap. They are just additional ways to install it, and different preprocessors that you can leverage.
I'm trying to setup mocha tests in my project using the globally installed mocha, which is the latest version (1.7.7 at the time of writing).
Instead of doing something, it opens my default editor and opens the file mocha.js. Running mocha does this; mocha test ., mocha --help, and npm test also gives the same result. Installing it locally produced the same effect.
Is this just some configuration error? Maybe I've missed a step during setup? Please advise me on how to fix this.
Nvm, I was just being dull. I had run mocha init ., which somehow messed it up.
Removing the generated mocha.js and mocha.css files did the trick.
If anyone could explain why this happens though, that'd be great! :)