radioactive-quality — All issues and discussion related to quality for the RadioActive project

[Radioactive-quality] (no subject)

[Ismail N. <mer...@pr...>]

hi Radioactive


http://tech-tips.ca/wp-content/showimage.php?largest=q2e7f6mq5q3s


Ismail Nalwala

[Radioactive-quality] Hi Radioactive

[Ismail N. <ena...@br...>]

Good evening Radioactive



http://zieloneblogi.pl/tight.php?produce=ampag1yq44p16b



ena...@ya...

[Radioactive-quality] aRt LS- L 0 LITA NOW is out !!! with 4 in1 tG4

[Best O. <dk...@op...>]

Hello Radioactive-quality,

At this time we can offer a small update at our system - LS-L0 LITA and LITTLE CUTIES!
Studio and our little stars are proud to present their new project. You can 
now compare this one with our other sites, judge the level of professionalism 
and exposure of subject, with have never been so high! Starign from over 
4,000 HQ pics, the project features sets made in the studio, as well as on 
the side of nature.         

             http://frost.offer4in1.com/6/?aspen
  
Our great and unique offer: for each subscribtion You get access to another
three sites from our portal for 31 days... without any additional payments!
Simply subscribe, select and use!

MSGID: drOV4I8HLbYWBRunreasonablenessT3Do5xhnFTfi0l

[Radioactive-quality] RE: http://developers.radioactivehq.org

[Somen M. <som...@ra...>]

Hi Guys,

We put up a new web site just for the RA team.  It's located here:
http://developers.radioactivehq.org/

Basically, this website will be the team's internal hub and will provide
information and resources.  We will post how-to documents, tasks, timelines,
roles, etc.  Check it out and email me if you have any suggestions.

Thanks,
Somen

[Radioactive-quality] more unit testing

[Shaun R. <sha...@ra...>]

Ismail,

I am glad to hear that you have a good deal of JUnit experience. =A0I have =
been=20
doing a LOT of reading on this over the past week or so, and it differs a b=
it=20
from the way I am used to doing unit testing, but I really like it from wha=
t=20
I have read so far. =A0It seems to allow for a very efficient way of unit=20
testing, without disrupting the development process. =A0Hopefully when we g=
et=20
into development you can use your experience and give us all a bit of=20
guidance on this.

I agree with you on the code inspection process (or code reviews). =A0We ca=
n=20
visit this again when we get closer to development. =A0I like the discussio=
ns=20
we are having, I think we are well on our way to having a quality app.

Thanks,
Shaun

[Radioactive-quality] more unit testing

[Shaun R. <sha...@ra...>]

Ismail,

I am glad to hear that you have a good deal of JUnit experience.  I have been 
doing a LOT of reading on this over the past week or so, and it differs a bit 
from the way I am used to doing unit testing, but I really like it from what 
I have read so far.  It seems to allow for a very efficient way of unit 
testing, without disrupting the development process.  Hopefully when we get 
into development you can use your experience and give us all a bit of 
guidance on this.

I agree with you on the code inspection process (or code reviews).  We can 
visit this again when we get closer to development.  I like the discussions 
we are having, I think we are well on our way to having a quality app.

Thanks,
Shaun

[Radioactive-quality] Re: unit testing

[Ismail N. <ena...@ya...>]

Shaun,

I have used Junit for the last 3 years.. we can talk about it whenever
you like.

If we start to use java which seems very likely at this point, most
developers comming in from that background hopefully have some unit
testing effort. 

Unit tests are extremely effective if done regularly by the developer.
They just increase your overall quality and productivity substantially.
There are tons of books and articles writen on this stuff by experts
like Martin Fowler, Kent beck etc.. There is a learning curve.. but it
pays off. 

Also I agree that more sets of eyes the better. For that we need to
setup a process for inspecting code. Maybe whenever a new development
artifact or any piece of is submitted we should have an informal code
inspection process. Thats how a lot of the big projects do it. You
submit the code they inspect the code and then include the code with a
build.

--- Shaun Ricci <sha...@ra...> wrote:

> Hey everyone,
> 
> I am not sure if we are too early into the development cycle to start
> thinking 
> about unit testing, but I want to always be keeping things like this
> in the 
> back of my head so when it comes time to unit test we are not
> wondering what 
> direction to go in.  Here is a real quick summary of some things I
> think 
> about on unit testing.
> -should be done by the developers.  Generally in the past, as a rule
> of thumb 
> I have not unit tested my own code.  The more sets of eyes on a piece
> of 
> code, the more stable it will be.  
> -someone from the quality ensures that unit testing is done on every
> line of 
> code.
> -it seems we are leaning towards java, and if that is the case, does
> anyone 
> have experience with JUnit?  I don't, but have been trying to play
> with it a 
> bit.
> 
> I have lots of other thoughs on unit testing, so perhaps we can talk
> about 
> this more over IRC in the next couple of weeks.  Any suggestions are
> more 
> than welcome.  There are alos other quality subjects I want to talk
> about 
> (regression testing etc.), and will send out other emails so we can
> get 
> threads on each sub -topic we discuss over time.
> 
> Thanks,
> Shaun
> 


=====
Ismail Nalwala                       email:ena...@ya...

[Radioactive-quality] unit testing

[Shaun R. <sha...@ra...>]

Hey everyone,

I am not sure if we are too early into the development cycle to start thinking 
about unit testing, but I want to always be keeping things like this in the 
back of my head so when it comes time to unit test we are not wondering what 
direction to go in.  Here is a real quick summary of some things I think 
about on unit testing.
-should be done by the developers.  Generally in the past, as a rule of thumb 
I have not unit tested my own code.  The more sets of eyes on a piece of 
code, the more stable it will be.  
-someone from the quality ensures that unit testing is done on every line of 
code.
-it seems we are leaning towards java, and if that is the case, does anyone 
have experience with JUnit?  I don't, but have been trying to play with it a 
bit.

I have lots of other thoughs on unit testing, so perhaps we can talk about 
this more over IRC in the next couple of weeks.  Any suggestions are more 
than welcome.  There are alos other quality subjects I want to talk about 
(regression testing etc.), and will send out other emails so we can get 
threads on each sub -topic we discuss over time.

Thanks,
Shaun