Wiki Documentation

[Michael Labriola]

Would any of the folks on here be willing to spend some cycles going
through the wiki? There is a lot of confusing information and
misinformation there as folks have edited or added something along the
way but sometimes it is marginally correct or a workaround when they
didn't completely understand the problem.

If anyone is willing, I am more than willing to help you with the
technical content. By that I mean,if someone takes a section of the
wiki and is willing to work on it, I will be glad to spend some time
phone/connect/etc. filling in any details or answering questions about
it to ensure you have all of the needed information.

This is a separate effort from any of the more structured efforts
being lead by Joel or Simeon. I see this as necessary stop gap to help
new users.

Thanks,
Mike

[Costin Aldea]

  Oke! I'm in. Waiting for  details on the tasks. Tx

2010/10/10 Michael Labriola <malab...@gmail.com>

--
P R O U D L I N U X F E D O R A U S E R
Sustain free open-source community
            Free as in free speech!

[Michael Labriola]

Excellent.

First thing would be to have you go through the steps, starting at this page:

http://docs.flexunit.org/index.php?title=Introduction

And just hitting next until the introduction is done. I would like you to read through the text, look for any mistakes and follow all of the steps running all of the code samples. If anything doesn't work, or isn't clear enough, let's just schedule a call to discuss and provide detail.

I fixed a few inaccuracies this morning and I just want to give our new users the best shot.

I ma guessing it will take an hour or two of total time.

Thanks so much,

Mike

[Robert Penner]

This section could use a bit of explanation:

"Using a UIListener and TestRunner"
http://docs.flexunit.org/index.php?title=Setting_up_a_FlexUnit_4_Project

Initial questions the reader could have: "What is a UIListener? Which
UI is being listened to? I'm not testing UI in my library; do I need
this?"

Of course *we* know the right answers, but I don't think it's obvious
that "UIListener" is listening to the test results (not to a UI) and
displaying them *in a UI*.

Robert

[Michael Labriola]

Excellent points. I appreciate everyone looking at these with critical eyes. The most important thing to me is getting new users testing. If we create any artificial barriers it increases the odds that they abandon before they begin

[Costin Aldea]

Whouldn't it be great to have integration instruction for FDT too (3
and 4) in this chapter Setting up a FlexUnit 4 Project ? Some people
are using FDT and it's a great tool. I'd love to see that too.

2010/10/11 Michael Labriola <malab...@gmail.com>

[Costin Aldea]

Definitions before usage of terms.
Noticed the usage of flexunit terms like UIListener and TestRunner
starting from the Setting up a FlexUnit 4 Project page as Robert
mentioned. My opinion is that it would more exhaustive to have them
defined into the page Terminology before being used into the FlexUnit
4 Project page . So that would mean having the page terminology before
Setting up a FlexUnit 4 Project or terminology could be managed in a
different thread. Wait for feedback on that. Tx

2010/10/12 Costin Aldea <costi...@gmail.com>:

[Michael Labriola]

Agreed. I would love to see those instructions here

[Michael Labriola]

I am okay with a terminology page, but we then need to be diligent about making sure we link to that page everywhere