Re: [Elementary-dev-community] about TDD (Test Driven Development)

>also we're not talking on mere theory or philosophy; we posted real code, examples and documentation; also real-life experience. This is a sane discussion. We don't need hypothetical examples on hypothetical apps, we want real examples on real apps. On Tue, Sep 3, 2013 at 4:08 PM, Daniele S. w

Re: [Elementary-dev-community] about TDD (Test Driven Development)

What do you mean "real apps"? As long as the code executes, I don't see the value in the distinction. On Sep 3, 2013 2:30 PM, "David Gomes" wrote: > >also we're not talking on mere theory or philosophy; we posted real code, > examples and documentation; also real-life experience. This is a sane >

Re: [Elementary-dev-community] about TDD (Test Driven Development)

ok then, https://code.launchpad.net/~oppifjellet/cable/message-history in this branch I implemented some basic tests on the feature I added ( message history on cable irc client ) using GLib.Test. Refer to my last commit ( http://bazaar.launchpad.net/~oppifjellet/cable/message-history/revision/128

Re: [Elementary-dev-community] about TDD (Test Driven Development)

> > Please make your energy useful in more useful ways > Dear TTD proponents, while you keep spending lots of time on writing these mails and the time of all the other devs on reading them, ~alourie is looking into Autopilot and experimenting with writing tests using it. I encourage you to follow

Re: [Elementary-dev-community] On compiler warnings

So we can suppress C warnings altogether - good! I hear Midori has moved to CMake (W00T FINALLY!!!), so we could probably just copy the relevant snippents from its CMakeLists.txt? What are those snippets exactly? -- Sergey "Shnatsel" Davidoff OS architect @ elementary -- Mailing list: https://l

Re: [Elementary-dev-community] about TDD (Test Driven Development)

We don't write backends so we shouldn't have anything to unit test. By far the most of the code we write deals with GUI and thus should be tested using Autopilot. Even if we do have something to *unit* test, the added complexity, higher entry barrier and the time spent writing first the unit testi

Re: [Elementary-dev-community] about TDD (Test Driven Development)

Sergey, Autopilot and Unit tests are not the same thing. In fact, from the same Autopilot documentation: "" Autopilot exists at the apex of the “testing pyramid”. It is designed to test high-level functionality, and complement a solid base of unit and integration tests. *Using autopilot is not a

Re: [Elementary-dev-community] about TDD (Test Driven Development)

Hi, Are weseriously having another thread on TDD? ~alourie said in this thread and very well: >I believe that this has been discussed quite thoroughly already. For now, TDD as a development philosophy is not really appropriate for the eOS development. That is not a direct result of tools missing

Re: [Elementary-dev-community] about TDD (Test Driven Development)

I don't think this is necessarily a bad idea, but I think the real issue isn't that glib.Test is incomplete, but that it might lack a lot of convenience utilities. I think the community should get some experience with glib.Test before we go and wrote or own testing packages. Then when we do wrote t

Re: [Elementary-dev-community] about TDD (Test Driven Development)

I don't see how the test suite relates to Granite but yes; it would be helpful ( and hard ) to build something on top of GLib.Test to ease the writing of unit tests. But the best approach IMHO is to adapt Vala to support TDD. Something like this: class Demo : Object {public void random_strin

Re: [Elementary-dev-community] about TDD (Test Driven Development)

So, if TDD is so good and GLib.Test is so bad or incomplete, why not to extend it in something like Granite.Test? would be that possible? useful? hard? 2013/9/3 Alex Lourie : > I believe that this has been discussed quite thoroughly already. For now, > TDD as a development philosophy is not really

Re: [Elementary-dev-community] about TDD (Test Driven Development)

I believe that this has been discussed quite thoroughly already. For now, TDD as a development philosophy is not really appropriate for the eOS development. That is not a direct result of tools missing for unittesting, but again, a development process decision. That said, I think that testing is i

Re: [Elementary-dev-community] about TDD (Test Driven Development)

I do understand your point, and I agree with that. But what I want to discuss is not if the TDD is generally a good approach ( hint. it is ) but if it's the right approach for a community driven project like elementaryOS. about this statement: "So if you can test something in a language (if its bu

Re: [Elementary-dev-community] about TDD (Test Driven Development)

Hello, TDD isn't a Technic its a mindset or a philosophy. It came from the Agile manifesto http://agilemanifesto.org/  . So if you can test something in a language (if its build in or not) you can run do TDD. Often young developers don't see the need for writing t

[Elementary-dev-community] about TDD (Test Driven Development)

I read some threads focusing on TDD, so I wanted to create one where we can continue that conversation without being offtopic. I'd say my two cent about TDD and elementary os development. In my opinion our current environment is obstile to TDD for serveral reason: 1. Vala doesn't support TDD out