Quoting the official readme for https://atmospherejs.com/practicalmeteor/mocha:
A package for writing and running your meteor app and package tests with mocha...
Differences with mike:mocha
...We do not support writing mocha tests for your app's code... Only code in packages can be tested with this package.
The text contradicts itself, so what is the truth?
That's a mistake in the Readme, App testing is supported
Originally (~Aug 2015) practicalmeteor:mocha only supported package testing, as the differences section says
They added support for App tests later on (~Mar 2016) and added the "App testing with meteor test" section
It seems they forgot to update the differences part
Related
I have been trying to execute R code on U-SQL using the R extensions mentioned in the documentation (https://learn.microsoft.com/en-us/azure/data-lake-analytics/data-lake-analytics-u-sql-r-extensions).
When I try to execute the example scripts mentioned in the link above, it throws the error:
C# error CS1739: The best overload for 'Reducer' does not have a parameter named 'rReturnType'
And when I remove the rReturnType parameter I am unable to make sense of the output.
Are there any other Extension.R parameters which will serve the same purpose?
Which version of the extensions have you installed? if you installed them some while ago, the parameters of the libraries may have changed and be out of date with the documentation. I am pinging the owner of the documentation page to make sure that the docs are in sync with the latest released version.
UPDATE: I checked and the documentation is aligned with the latest version. Please go to the ADLA Portal and reinstall the U-SQL Extensions. Please make sure that you read up on the release notes in case you or someone else uses the older version.
I am trying to run a project on meteor but getting this error in the command line-
this project uses Meteor1.0.2.1, which isn't available on Windows. To
work with is app on all supported platforms, use ,meteor update
--release METEOR#1.1.0.2 to pin this app to the newest Windows-compatible release.
I have tried updating to which I am getting the error message
while checking for meteorhacks:kadira-binary-deps#1.2.1:error: No
compatible binary build found for this package. Contact the package
author and ask them to publish it for your platform.
I tried updating this to which i was brought back to the first error message.
Does anyone know how I can run this meteor package? It is sparrow-finance to be specific.
Regards
Chris
The answer is simply remove the kadira package which you can do by editing the packages file in .meteor.
But, kadira is really useful. So what I'd suggest is to set up meteor environments. Meteor cookbook has a good example of this - https://github.com/awatson1978/meteor-cookbook/blob/master/cookbook/environment-detection.md .
If your environment is anything other than local, use kadira, else don't use it.
Velocity is an amazing testing framework for Meteor and I am currently using it to test my application code.
Now I added a local package to the app, but I don't know how (or if) I can test the package with Velocity, too. I would like to drop tinyTest in favor for a consistent testing framework - Velocity.
Is it possible to test packages with Velocity? How should the file structure look like?
Yes, it is possible to test packages with sanjo:jasmine. It works in nearly the same way as with TinyTest. You can find all information to get started in the sanjo:jasmine README. There is also an example package. To run the tests, use the commands from the README.
If you need additional information, let me know.
I'm trying to understand what the docs say about the meteor package server.
In addition to Isopacks, the Package Server contains distributions,
which are sets of packages that have been tested together by a release
engineer and that are known to work well together. For example, when
you use Meteor 1.0, you're using the METEOR distribution at release
1.0.
(https://www.meteor.com/services/package-server)
and
Other people can also publish their own distributions to the package
server as well. If developer alice published a distribution called
SPACE-ROCK, you could switch your project to it by typing something
like meteor update --release alice:SPACE-ROCK#1.2.
(https://www.meteor.com/projects)
I know I can browse packages thru meteor search ... or on atmosphere. But the distrubutions are not listed there.
Is there any way to search/list distributions published to the package server?
meteor search will show releases (I believe a 'distribution' is just a release), but from the documentation, I can't find any way to limit it to only show releases. Here's my result, as an example:
> meteor search
.... // literally all of the packages
Matching releases:
CORDOVA-PREVIEW An experimental release of meteor with Cordova support.
GITHUBBLE Release for githubble.meteor.com.
METEOR The Official Meteor Distribution
METEOR-CORE An experimental release of meteor.
WINDOWS-PREVIEW Preview of Meteor on Windows
diegosampaio:METEOR meteor 1.0.0 compatible
ekate:METEOR-SHOW Meteor Shows Things
ekate:REL-TEST test
ekate:TEST Packaging UX Wrangling
glasser:PUBLISHTEST Test release for isopack-cache branch.
glasser:TPS-PREVIEW Preview releases for tool performance and stability work.
glasser:UPDATE-TEST The official Meteor distribution.
konecty:METEOR meteor 1.0.0 compatible
lawshe:FULLPAGE Meteor smart package for FullPage.js. Create full screen pages fast and simple.
Correct me if I'm wrong, but a "build" is a "compile", and not every language compiles. Continuous Integration involves building components to see if they continue to work beyond unit tests, which I might be oversimplifying. But if your project involves a language that does not compile, how do you perform nightly builds or use continuous integration techniques?
Hmm... I'd define "building" as something like "preparing, packaging and deploying all artifacts of a software system". The compilation to machine code is only one of many steps in the build. Others might be checking out the latest version of the code from scm-system, getting external dependencies, setting configuration values depending on the target the software gets deployed to and running some kind of test suite to ensure you've got a "working/running build" before you actually deploy.
"Building" software can/must be done for any software, independent of your programming langugage. Intepreted languages have the "disadvantage" that syntactic or structural (meaning e.g. calling a method with wrong parameters etc.) errors normally will only be detected at runtime (if you don't have a separate step in your build which checks for such errors e.g. with PHPLint).
Thus (automated) Testcases (like Unit-Tests - see PHPUnit or SimpleTest - and Frontend-Tests - see Selenium) are all the more important for big PHP projects to ensure the good health of the code.
There's a great Build-Tool (like Ant for Java or Rake for Ruby) for PHP too: Phing
CI-Systems like Xinc or Hudson are simply used to automagically (like anytime a change is checked into scm) package your code, check it for obvious errors, run your tests (in short: run your build) and report the results back to your development team.
Create a daily tag of your current source control trunk?