Bernt Hansen writes:
> "Eric Schulte" writes:
>
>> So, I've been using the framework in the combined-testing branch this
>> morning writing tests to strap down my daily Babel bug fixes, and I'm
>> really liking ERT.
>>
>> I wonder, can we commit to the combined-testing branch, and if so could
>>
"Eric Schulte" writes:
> So, I've been using the framework in the combined-testing branch this
> morning writing tests to strap down my daily Babel bug fixes, and I'm
> really liking ERT.
>
> I wonder, can we commit to the combined-testing branch, and if so could
> we fold it into the master bran
Sebastian Rose writes:
> "Eric Schulte" writes:
>> Hi,
>>
>> So, I've been using the framework in the combined-testing branch this
>> morning writing tests to strap down my daily Babel bug fixes, and I'm
>> really liking ERT.
>>
>> I wonder, can we commit to the combined-testing branch, and if s
"Eric Schulte" writes:
> Hi,
>
> So, I've been using the framework in the combined-testing branch this
> morning writing tests to strap down my daily Babel bug fixes, and I'm
> really liking ERT.
>
> I wonder, can we commit to the combined-testing branch, and if so could
> we fold it into the mast
Hi,
So, I've been using the framework in the combined-testing branch this
morning writing tests to strap down my daily Babel bug fixes, and I'm
really liking ERT.
I wonder, can we commit to the combined-testing branch, and if so could
we fold it into the master branch? It would make my test driv
"Eric Schulte" writes:
> Hi,
>
> I've taken the liberty of merging our two testing branches into the new
> "combined-testing" branch. This now includes both ert and jump.el as
> git submodules, which can be installed with
>
> git submodule init
> git submodule update
>
> after checking out th
Hi,
I've taken the liberty of merging our two testing branches into the new
"combined-testing" branch. This now includes both ert and jump.el as
git submodules, which can be installed with
git submodule init
git submodule update
after checking out the branch. In merging the two org-test.el
"Eric Schulte" writes:
> "Eric Schulte" writes:
> To illustrate my suggestions, I've thrown together a couple simple Babel
> tests roughly following this outline, currently up in the
> `schulte-testing' branch of the Org-mode repo.
>
> To try it out
> 1) load the testing/org-test.el file
> 2) run
"Eric Schulte" writes:
> Hi Sebastian,
>
> Sebastian Rose writes:
>
>> "Eric Schulte" writes:
>>> Hi,
>>>
>>> This is exciting.
>>>
>>> Rather than impose a complete directory/layout schema before-hand I'd
>>> lean towards starting with a little more chaos and then letting the
>>> structure of t
"Eric Schulte" writes:
[...]
>
> Could we just load every test in tests/lisp by default, and then use the
> existing `ert' selection method to select and run tests. For example if
> we enforce our conventions on the level of test function name rather
> than on file name, we could (I believe) do
Hi Sebastian,
Sebastian Rose writes:
> "Eric Schulte" writes:
>> Hi,
>>
>> This is exciting.
>>
>> Rather than impose a complete directory/layout schema before-hand I'd
>> lean towards starting with a little more chaos and then letting the
>> structure of the test directory develop /naturally/.
"Eric Schulte" writes:
> Hi,
>
> This is exciting.
>
> Rather than impose a complete directory/layout schema before-hand I'd
> lean towards starting with a little more chaos and then letting the
> structure of the test directory develop /naturally/. From the
> discussion below it sounds like an i
Hi,
This is exciting.
Rather than impose a complete directory/layout schema before-hand I'd
lean towards starting with a little more chaos and then letting the
structure of the test directory develop /naturally/. From the
discussion below it sounds like an initial structure of
testing/lisp/
tes
On Oct 2, 2010, at 5:01 PM, Sebastian Rose wrote:
Carsten Dominik writes:
It would be OK to have a lisp subdirectory in testing,
just as it would be OK to have contrib/lisp in testing
for the contributed packages.
That's what it is like.
You probably did not notice, because "org-test.el" i
Carsten Dominik writes:
> It would be OK to have a lisp subdirectory in testing,
> just as it would be OK to have contrib/lisp in testing
> for the contributed packages.
That's what it is like.
You probably did not notice, because "org-test.el" is supposed to live
inside "testing/", so it's not
Carsten Dominik writes:
> Hi Sebastian,
>
> the lack of a testing suite for Org-mode is really frustrating,
> and even more frustrating is that we have had like seven attempts
> to start one, and each of these lead to nothing. So I would
> be perfectly happy to give a free hand, write access to t
Hi Sebastian,
the lack of a testing suite for Org-mode is really frustrating,
and even more frustrating is that we have had like seven attempts
to start one, and each of these lead to nothing. So I would
be perfectly happy to give a free hand, write access to the repo
and a full directory in the
17 matches
Mail list logo
