I have basic Galen testing set up on a responsive Angular site, running through a simple test on desktop and tablet versions of the site.
I did not build this site and cannot say if Galen ever fully worked properly on the website. I did myself upgrade Galen from v1.6.3 to v2.2.1 in NPM, which included updating syntax etc in the .test file and two .gspec files.
Almost everything appears to be working fine by the Gulp command I am running in Mac terminal:
GALEN_URL=http://localhost:3000/MYSITE/ gulp test:galen-local
This runs the test locally (vs SauceLabs). Via terminal, I see the two tests run, with test criteria printed out, and I get a note that there is a failure on tablet version (it's an easy CSS-related fix for tablet version, and I'm not worried about that). Also, I am getting the HTML reports for those two tests, written to a local directory.
My problem is the following error message I get after the tests run:
========================================
Failed tests:
Login page on tablet device
Suite status: FAIL
Total tests: 2
Total failed tests: 1
Total failures: 3
There were failures in galen tests
[13:51:04] 'test:galen-local' errored after 11 s
[13:51:04] Error in plugin 'gulp-shell'
Message:
Command `./node_modules/.bin/galen test tests/galen/tests/local.test --htmlreport galen-reports -DwebsiteUrl=http://localhost:3000/MYSITE/ -DsauceUser=USERNAME -DsauceKey=SAUCEKEY` failed with exit code 1
What is failed with exit code 1? I have searched Galen docs, searched the web, and I can't figure out what might be going wrong. I have no idea what that means.
I can provide more code if needed, but the website is relatively sophisticated and things are abstracted out across many files.
thanks for any assistance
I think I might have answered my own question just now...
When I removed the test criteria that were failing for tablet version, I got the following in terminal with no "command" error message:
========================================
Suite status: PASS
Total tests: 2
Total failed tests: 0
Total failures: 0
[14:24:16] Finished 'test:galen-local' after 11 s
I presume the command error message was just a reflection that tests in the overall suite were failing. Still, it seems odd to me that such an error message would appear after a Total failed tests: 1 Total failures: 3 message already made clear that certain tests in the tablet version were failing. And I still don't know what specifically the "error code 1" above means.
If anyone has any insight, feel free to chime in. Otherwise, I'll mark this as THE answer at some point, if I don't just delete the entire question.
Related
I use Java and Cucumber 7 and Allure dependencies and Plugin with Allure. The reports are created but I keep getting theses errors
ERROR io.qameta.allure.AllureLifecycle - Could not update step: no
step running
ERROR io.qameta.allure.AllureLifecycle - Could not stop
step: no step running
.
I've tried many things based on Google serach results but nothing helps
I don't want above error messages appear in my output log
None of the PHP Unit tests implemented run.
It doesn't throw errors either.
No errors are logged and the test keeps running infinitely.
C:\xampp_v7.0\htdocs\...>vendor\bin\phpunit --verbose tests\TestCase\Model\Table\UsersTableTest.php
PHPUnit 6.5.9 by Sebastian Bergmann and contributors.
Runtime: PHP 7.0.30 with Xdebug 2.5.5
Configuration: C:\xampp_v7.0\htdocs\...\phpunit.xml.dist
I restarted MySql server and this was fixed.
Another possible reason could be
Errors in the data loaded in Fixtures (Any syntax errors in the fixture files can lead to this situation) This can be identified by excluding all fixtures and including them one at a time and running the tests. Using this way the fixture that caused the issue can be found.
When you're running your suite of e2e tests via a CI server like Bamboo; you expect to come back the next day or hour to see a report showing how many tests passed/failed.
In my case, my e2e tests stop running as soon as a single test fails so I come back the next morning to check the nightly build and do not have that nice report showing the stats on what passed/failed.
Checking the log file, I can see that there were some cucumber features that passed earlier on in the log prior to the failed feature; but again, a failing feature halts/stops the execution of any further tests in my situation.
The error would look something like:
AssertionError: expected 'Green' to equal 'Red'
[launcher] BUG: launcher exited with 1 tasks remaining
error 17:59:29
error 17:59:29 C:\Users\bamboo-agent-home\xml-data\build-dir\PROJ\gulp\e2e-tests.js:27
error 17:59:29 throw err;
error 17:59:29 ^
error 17:59:29 Error: protractor exited with code 100
How can I force the test suite to continue running even if some features fails so that I can finally make it to that end report with the stats: passed/failed?
Could it be a conflicting issue between how Protractor handles promises vs how chai/chai-as-promised does?
Protractor v 4.0.1
Chai v 3.4.0
Chai-as-promise v ^5.1.0
Windows 10
cucumber#0.6.0 - **`I found this with npm list cucumber`**
Node v 4.4.7
Gulp
CLI version 3.9.1
Local version 3.9.1
My android build fails after build and this is the error log i get
Total time: 1 mins 16.631 secs
Stopped 0 compiler daemon(s).
Received result Failure[value=org.gradle.initialization.ReportedException: org.gradle.internal.exceptions.LocationAwareException: Execution failed for task ':dexRelease'.] from daemon DaemonInfo{pid=5907, address=[10331ba5-2501-41cc-aa13-52a0ba46bd51 port:41817, addresses:[/0:0:0:0:0:0:0:1%1, /127.0.0.1]], idle=false, context=DefaultDaemonContext[uid=2862cb6d-50e8-4321-a1fa-590435e89f0f,javaHome=/usr/java/jdk1.7.0_67,daemonRegistryDir=/home/ec2-user/.gradle/daemon,pid=5907,idleTimeout=120000,daemonOpts=-XX:MaxPermSize=512m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1500m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]} (build should be done).
This is probably related to this: https://www.codenameone.com/blog/video-new-defaults-barcode-qrcode-changes.html
You can workaround this by using android.gradle=false in the build hints. However, I'm guessing its related to some cn1lib or build hint you added. But it seems the build error log you provided is partial so I don't see any issue there.
This is my first time using Angular (and Karma), so please excuse me if this is a total beginner's question: that's what I am.
I'm trying to run the Angular-phonecat tests, as described in Step 02 - Writing and Running Tests
My code is checked out directly from the step 2 branch (git checkout -f step-2)
When running the test (angular-phonecat\scripts> test), I'm given the following message:
INFO [karma]: Karma v0.10.2 server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
INFO [Chrome 30.0.1599 (Windows 7)]: Connected on socket Jw-2z-zZ-pytGNN-SHRM
Chrome 30.0.1599 (Windows 7): Executed 0 of 0 ERROR (0.472 secs / 0 secs)
There is no more information given, and I cannot find any log the would detail the problem (nothing in /test or its sub-directories, nor in /logs). I also cannot find a log for karma in general - is there one?
You need to add this line to karma.conf.js
exclude: ['app/lib/angular/angular-scenario.js'],
Theres an issue relating to this problem here: https://github.com/angular/angular-phonecat/issues/71
Hi i started today with angular and karma aswell, im on a mac and i have the same problem.
I joined the IRC channel #angularjs at freenode and asked for some help and this is the answer that i got.
[16:59] <Wirde> Hi, I just started with the Angular-phonecat tutorial, after installing karma and the adapters I got too step 2 but when I try to run the unit tests it gives me the error: Executed 0 of 0 ERROR (0.327 secs / 0 secs). Can some please tell me whats wrong?
[17:00] <dmco> Wirde: I think phonecat is wonky after some 1.2rcX upgrades
[17:01] <dmco> Wirde: Another guy was complaining about issues with it yesterday
[17:02] <Wirde> dmco: hi, thanks for the answer, how do you suggest i proceed? Is there another good way to learn about karma and testing with angular?
[17:02] <rdepena> http://www.yearofmoo.com/2013/01/full-spectrum-testing-with-angularjs-and-karma.html#karma
[17:02] <dmco> Wirde: One easy way would be to scaffold a new project using Yeoman and the AngularJS generator
[17:02] <rdepena> this is a great source
[17:02] <dmco> ^^ Wirde that is a good link too
[17:03] <Wirde> dmco: rdepena: Thank you for the help! I will check it out :D
Not sure if this is the response that you wanted or if its enought but i tought i might share it.