[openbeostranslationkit] Re: Roll Call

> I can understand that. I'm trying to work, finish up my 
> computer science degree and write code on the side too.
I'm a second year Computer Science and Engineering student, though I
have experience prior to coming to school. So that's a big part of my
time. 
> 
> I hate to sound like a newbie, but what is happening with the 
> Translation Kit right now and what should I work on? Or if 
> there is no set direction right now, what could I do that 
> would be helpful for the team?
Right now I'm working on a set of documents to tell us where we are
going with this. At the moment I really don't have anything written as
much as just a large collection of ideas. If anyone wants to add to this
they are welcomed to, or provide any documentation. If there's anything
you want to do, you are welcomed to. 

We need some unit testing stuff. Take a look at a class and figure out a
good way to test the class. 

Right now I see:

1. Testing constructors, and making sure they provide the correct data.
2. Testing access and modifying methods.
3. Testing other methods.
4. Testing operators.
5. Testing what ever else is left for the class.

How I see it :

We should have a set of 'correct' data. We write a small program to test
first the correct data with the original class. We may end up using this
to provide our test data as well. Then as we finish up the class we can
test more and more.

Output of this small program would be like:

Testing <class>
...
Now testing data set 1.
Default constructor... Good.
Copy constructor... Good.
Some other constructor... Failed - show expected data vs. provided data.

---------

Another point is coding standards. Pretty much everything covered by the
overall openbeos standards and also: all variables will have a comment
describing them, unless it's something like a counter (i.e.. int i).  

-----


As that stands, I want the tests completed before we begin creating the
library itself. And then, pick a class, and build. 

Comments / Input on what I have here would be good. Or if someone wants
to write it up this weekend, that would be fine as well.

That's all I have for right now, Enjoy everyone.

----
Travis Smith
sage at ieee dot org

Other related posts: