Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of braden@google.com designates
 209.85.216.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CA+GVa3auAnxwMofdUpUQBd7pNrC1x6phPWL-spRevxmFL6UHQw@mail.gmail.com>
References: 
 <CAMk5LLk6j1rqSHoTSqjyPYC=ePrHEycV2R-UuzhwCw8fyHKKnQ@mail.gmail.com>
	<b5437805c92e492497b1787793c56b7c@BN1PR07MB135.namprd07.prod.outlook.com>
	<CA+GVa3auAnxwMofdUpUQBd7pNrC1x6phPWL-spRevxmFL6UHQw@mail.gmail.com>
Date: Mon, 25 Nov 2013 14:47:50 -0500
Message-ID: 
 <CAMk5LLmJ6MVmPv+yu-2+JGLrLs0_cSL_vY+UGrm5w9oEjB-pUg@mail.gmail.com>
Subject: Re: Refactoring the CLI tests
From: Braden Shepherdson <braden@google.com>
To: Mark Koudritsky <kamrik@google.com>
Cc: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=047d7bdc06289450d904ec05a395

--047d7bdc06289450d904ec05a395
Content-Type: text/plain; charset=ISO-8859-1

I think they're ready to go, yeah.

Remember not to rebase the branch, since it's shared; just merge.

Braden


On Mon, Nov 25, 2013 at 2:15 PM, Mark Koudritsky <kamrik@google.com> wrote:

> Would it be ok to merge the e2e tests to master now?
> I did a change <https://reviews.apache.org/r/15775/> last week and a test
> for it will be much better and easier in the e2e tests (got it ready
> locally). So I'm starting to depend on the e2e tests.
>
>
> On Thu, Nov 14, 2013 at 2:02 PM, Jonathan Bond-Caron <
> jbondc@gdesolutions.com> wrote:
>
>> On Thu Nov 7 11:40 AM, Braden Shepherdson wrote:
>> > The CLI tests are bad. I propose making them better.
>> >
>> > I propose letting the tests actually run filesystem and related calls,
>> instead of
>> > always mocking them out. In the simplest form, that means running them
>> on the
>> > real filesystem. If that's too slow, we can investigate other
>> alternatives, like using
>> > a ramdisk, or using that emulated fs that runs everything in RAM inside
>> Node.
>> >
>>
>> Big +1, the cli tests are failing on windows:
>> https://issues.apache.org/jira/browse/CB-5330
>>
>> Wouldn't be caught if it was mock tests.
>>
>> For the emulated 'fs', it could be a proxy pattern to a file system on
>> RAM:
>>
>> e.g.
>> testfs.setRoot('Z:\cordova-test');
>> testfs.init();
>>
>> // init() would remap every fs function
>> var fs = require('fs'), map = {'mkdir': fs.mkdirSync};
>>
>> fs.mkdirSync = function (path, mode) {
>>   return map.mkdir(testfs.getPath(path), mode);
>> };
>>
>> // using the default fs functions during tests is remapped to a virtual
>> root path
>> fs.mkdirSync("C:\somewhere\cordova\foo"); // chmod
>> 'Z:\cordova-test\C\somewhere\cordova\foo '
>> fs.mkdirSync("/somewhere/cordova/foo");    // chmod
>> '/mounted/tmpfs/somewhere/cordov/foo '
>>
>> Tmpfs is great on unix, for Windows, I use:
>> http://www.softperfect.com/products/ramdisk/
>>
>>
>>
>

--047d7bdc06289450d904ec05a395--