seen from Canada
seen from United States
seen from United States
seen from Malaysia
seen from United States
seen from United States
seen from Türkiye
seen from Australia
seen from Brazil
seen from United States
seen from Canada
seen from United States
seen from China
seen from United States
seen from China
seen from Türkiye
seen from United States
seen from Malaysia
seen from United States
seen from United States
Only Run 1 Test (Karma/Jasmine)
Only Run 1 Test (Karma/Jasmine)
Useful hack to only run 1 test in Karma.
Instead of ‘it’, change test declaration to ‘fit’. Example: fit('should create', () => { expect(component).toBeTruthy(); }); [\code]
This will force Karma to only run 'should create' test.
View On WordPress
Fixed What is a reasonable code coverage % for unit tests (and why)? #dev #it #asnwer
Fixed What is a reasonable code coverage % for unit tests (and why)? #dev #it #asnwer
What is a reasonable code coverage % for unit tests (and why)?
If you were to mandate a minimum percentage code-coverage for unit tests, perhaps even as a requirement for committing to a repository, what would it be?
Please explain how you arrived at your answer (since if all you did was pick a number, then I could have done that all by myself ;)
Answer: What is a reasonable code coverage % for…
View On WordPress
How to: How can I unit test a GUI?
How to: How can I unit test a GUI?
How can I unit test a GUI?
The calculations in my code are well-tested, but because there is so much GUI code, my overall code coverage is lower than I’d like. Are there any guidelines on unit-testing GUI code? Does it even make sense?
For example, there are graphs in my app. I haven’t been able to figure out how to automate the testing of the graphs. It takes a human eye, AFAIK, to check if the…
View On WordPress
How to: Clearing coverage highlighting in Eclipse
How to: Clearing coverage highlighting in Eclipse
Clearing coverage highlighting in Eclipse
After running coverage reports in Eclipse (using cobertura or an EMMA plugin), my source code files get highlighted in green, red and yellow depending on which lines of code were covered by tests.
How can I clear this highlighting after I’m done?
Answer: Clearing coverage highlighting in Eclipse
Click the “Remove all Sessions” button in the toolbar of…
View On WordPress
Fixed Code Coverage for C#/.NET #dev #it #asnwer
Fixed Code Coverage for C#/.NET #dev #it #asnwer
Code Coverage for C#/.NET
I wonder what options there are for .net (or C# specifically) Code Coverage, especially in the Lower Priced segment?
NCover
Seems to be very popular and looks quite good
Supports statement coverage and branch coverage
$480 for “NCover 3 Complete”
Older Beta-Versions available for free
Visual Studio (2008 Pro) | (2005 Team System (Development, Test or Team Suite…
View On WordPress
How to: Code Coverage for C#/.NET
How to: Code Coverage for C#/.NET
Code Coverage for C#/.NET
I wonder what options there are for .net (or C# specifically) Code Coverage, especially in the Lower Priced segment?
NCover
Seems to be very popular and looks quite good
Supports statement coverage and branch coverage
$480 for “NCover 3 Complete”
Older Beta-Versions available for free
Visual Studio (2008 Pro) | (2005 Team System (Development, Test or Team Suite…
View On WordPress
Enable Xdebug in MAMP
Enabling Xdebug in MAMP is really easy if you know where to look. Many thanks to Danne Lundqvist for sharing this delicious bit of information on his blog.
The Xdebug configuration directives are located in your php.ini file, which can be found at:
/Applications/MAMP/bin/php/php5.4.10/conf/php.ini
You'll most likely need to replace "php5.4.10" in the above path with the php version you are running. To find out what version of php you are running just type in your terminal:
which php
Open the php.ini file and at the bottom you'll see the Xdebug configurations. Simply remove the semi-colon at the beginning of the following line:
;zend_extension="/Applications/MAMP/bin/php/php5.4.10/lib/php/extensions/no-debug-non-zts-20100525/xdebug.so"
Save the file and restart MAMP.
If you have phpunit installed, you can now run code coverage with the --coverage-html=coverage; argument.
Build badges and dependencies status
Magnum CI is getting better and better with every new release. Today we rolled out a few new features that will help to improve the overall project codebase quality.
Build Badges
Build coverage and dependencies status badges are the new addition to the build details interface. It gives you a quick overview on how your project's code is covered and its dependencies status. OpenSource moves fast and every day brings more updates to popular libraries. Magnum CI will help you keep your codebase up to date.
Dependencies Status
Every time you push code (Ruby or Node.js) Magnum CI worker will evaluate dependencies status and generate a detailed report that you can view by clicking on "dependencies" badge.
Email Alerts
Too busy to check website for updates? No worries, Magnum CI will include coverage and dependencies status alerts in build email notifications:
Dont need code coverage or dependencies? Simply disable unwanted features in project settings:
Stay tuned for more updates!
