ctures of people and make a blog
> post somewhere about this (perhaps elementaryupdate), it's great PR for us
> and it was an awesome idea!
> >
> > Thank you and good job!
> >
> > ~David "Munchor" Gomes
> >
> >
> > On Wed, Aug 21, 2013 at 8
Hello guys and Girls,
First of all I'd mention that here in my
society/locality/streets/region/state linux is not quite popular (Hell,
some people doesn't even know what a linux is!), so I went out and told
them an evening :)
Two days ago I burnt 10 CD of luna and wrapped them in an envelop with
2013 at 11:02 PM, Albert Palacios wrote:
> Hi Craig and Gufran,
>
> I don't agree with TDD, and making a committee. Can you prove that there
> will be huge benefits in time/resources? Can you prove that there will be
> less bugs? (looks like that if tests are not right, bugs wil
Count me in.
I cant really put forward any point on how should we proceed but I'd
definitely love to be with the team.
Yes, a *testing committee* is a good idea, maybe something independent of
dev community. We can write scripts to automate tests, and we can do that
in any language (Python for exam
Yes exactly.
That is how tests works.
On Aug 19, 2013 2:37 PM, "A. "Xylon" V." wrote:
> So if I understand correctly, in TDD there is a specific bit of code (lets
> call it C) that you build a test for. Then, instead of using the
> application and trying to trigger code C, you invoke the test whi
Guys, Here is a conversation I and Craig had a while ago. The mail was
dispatched to Craig's personal inbox by mistake.
Here it is
*ME:*
*
*
I have read the book "*How google tests softwares*" and not to say that TDD
is a great tool to hit on both productivity and maintenance but I
personally thin
6 matches
Mail list logo
