Nor am I. But I think the first step would be to explore what can be done
with the existing tools (assuming there are any that are still supported).
I find that I rarely need much more than a simple facility with the ability
to create test cases and do setup/teardown so if we can find anything that
+1
Sergey, that page is massive. Could you send us the interesting parts?
On Thu, Apr 4, 2013 at 11:59 AM, Goncalo Margalho wrote:
> Sergey, how do you write code in Vala and write tests in C? it becomes too
> difficult for a developer, don't you think?
>
>
> On Thu, Apr 4, 2013 at 5:18 PM, Ser
Sergey, how do you write code in Vala and write tests in C? it becomes too
difficult for a developer, don't you think?
On Thu, Apr 4, 2013 at 5:18 PM, Sergey "Shnatsel" Davidoff <
ser...@elementaryos.org> wrote:
> I'm not so sure we need a solution bound to Vala specifically, because:
>
>1.
I'm not so sure we need a solution bound to Vala specifically, because:
1. We have automated UI testing covered by Ubuntu's regression testing
framework
2. We have D-bus testing coverted by Ubuntu's regression testing
framework
3. Vala translates to C so we can use a C unit testing
I would be interested but I'm not the best vala developer for sure.
On Thu, Apr 4, 2013 at 4:40 PM, Craig wrote:
> If we can get a number of experienced test practitioners and Vala
> developers to commit to it, I wouldn't mind contributing to a test
> framework development. Would anyone else be
If we can get a number of experienced test practitioners and Vala
developers to commit to it, I wouldn't mind contributing to a test
framework development. Would anyone else be interested?
On Thu, Apr 4, 2013 at 10:13 AM, Craig wrote:
> *Would it be feasible to create a Unit Test team on launch
*Would it be feasible to create a Unit Test team on launchpad with the sole
purpose of specializing in adding testing to projects and writing the tests
required to kill regression bugs before they kill us? - Dane*
*
*
If we do this, I would expect it to be short term only. Developers should
be resp
Craig, thanks to make everything more clear.
Unit test is not just having something to compare stuff but we need a great
mocking system. Does anyone have links for that as well?
On Thu, Apr 4, 2013 at 4:00 PM, Craig wrote:
> *If anyone is interested in starting a Vala Unit Test project under th
*If anyone is interested in starting a Vala Unit Test project under the
umbrella of the elementary community, I'm sure we could get quite a bit of
traction from the Vala community at large and I would love to help out. -
Dane Henson*
*
*
Not only that, but I imagine it would garner quite a lot of p
We do unit and behavorial testing at where i work, and i think it's great.
Writing tests before you develop the actual feature really makes you think
why your feature should do what and when it should do so.
Maybe we could build vala tests for granite. That would mean we would have
to write tests
Here is another practical post I found interesting regarding setting up
Unit Tests in Vala with Cmake:
http://blog.remysaissy.com/2012/11/setting-up-unit-tests-in-vala-project.html
I apologize for spamming the mailing list.
On Thu, Apr 4, 2013 at 8:56 AM, Sergey "Shnatsel" Davidoff <
ser...@ele
I strongly recommend anyone interested in automated testing to read through
Martin Pitt's Ubuntu Dev Week session on the topic. He's the one
responsible for most of unit testing in Ubuntu (he's also the author of
Apport which we already use). His IRC nick is "pitti" and the session logs
can be foun
I love this topic.
David Gomes, you said that writing tests is boring, probably you are right
but that's because you tried to write them in the "second approach"
explained earlier by Dane Henson.
The problem with that is that the code that you wrote before MAYBE is not
testable, which makes your l
2013/4/4 Craig
> Sergey, that looks very interesting, although I'm a little confused--what
> are the differences between your first link and Glimpse?
>
My first link is my scripts for easily testing code proposed for merging. I
created them to offload the burden of testing proposed code from dev
David,
I understand where you're coming from and I have worried about that in the
past. There are two approaches for Unit Testing.
The strong approach is to figure out what you want the app to do (i.e.
design the framework), describe that app's functions and libraries using
tests, then write your
We also had a regression on Granite the other day. It goes "I fixed this
bug" and I tested that bug but then I didn't test crazy-weird behaviour and
it turned out it broke some things. Of course, action has been taken to fix
it, but it can't be merged yet.
(sorry for sending this email to Cody twi
Our m̶o̶s̶t̶ ̶e̶f̶f̶e̶c̶t̶i̶v̶e̶ only regression testing is in Files. It
goes "Cody, I think I fixed crash X" and I add it to my list of crash
report email titles I look for to reoccur.
On Thu, Apr 4, 2013 at 8:25 AM, David Gomes wrote:
> Unit testing is boring to write so if we just said "Eve
Unit testing is boring to write so if we just said "Everybody. Write unit
tests. All Projects. Now." it would really take on. On companies and when
developers are paid to work, they can write and put tests everywhere, but
it's harder for us.
For now what we just do is we test the interface, the ne
Craig, I have seen that and it looks promising. That post also mentions
Yorba and valadate, but the Yorba devs have told me they have no intention
of continuing development on it.
On Thu, Apr 4, 2013 at 8:15 AM, Dane Henson wrote:
> Yes, testing is sorely needed.
>
> I started down the path of
Yes, testing is sorely needed.
I started down the path of finding the best solution for Vala Unit Testing,
but couldn't find any great options. Currently, all projects that pursued
the xUnit (https://en.wikipedia.org/wiki/XUnit) model for Vala have fallen
out of development and only their shells
I just came across this: http://esite.ch/2012/06/26/writing-tests-for-vala/.
It sounds very, very relevant. Comments?
Also, at work, we have a build server that kicks off a new build (and tests
immediately thereafter) roughly every time someone pushes changes to the
repo (sorry if that's not bzr t
This is what I've developed for testing:
https://lists.launchpad.net/elementary-dev-community/msg01948.html
I've also created Glimpse - a system for sandboxed testing, but it lacks a
D-bus proxy which is needed for adding/removing apps via GUI. See
http://shnatsel.blogspot.com/2011/07/weve-just-re
Individual comment from a non-dev who has just observed devs: it would seem
we have no formal testing policy but that we gravely need one. Code is
developed and requested to be merged by dev A, then dev B looks the code
itself over. Hopefully at this point dev B would then build it and test the
cra
Hello everyone,
I'm curious what you devs do for testing? I'm not particularly familiar
with Vala, but I'm learning a lot about testing at work and I'm trying to
develop myself to that end in my free time. I'm sending this email because
I'd like to get a pulse on what you Elementary devs think abo
You should take a look at the code. I don't remember how it is used.
—
Sent from Mailbox for iPhone
On Wed, Apr 3, 2013 at 10:56 PM, David Gomes
wrote:
> Do you know how hard it would be to make Files stop using IconFactory.vala?
> On Mon, Apr 1, 2013 at 7:45 PM, Mario Guerriero wrote:
>> Files
25 matches
Mail list logo
