- Home
- Pattern Languages
- Liberating Voices (English)
- Liberating Voices (other languages)
- Liberating Voices (Arabic)
- Liberating Voices (Chinese)
- Liberating Voices (French)
- Liberating Voices (German)
- Liberating Voices (Greek)
- Liberating Voices (Hebrew)
- Liberating Voices (Italian)
- Liberating Voices (Korean)
- Liberating Voices (Portuguese)
- Liberating Voices (Russian)
- Liberating Voices (Serbian)
- Liberating Voices (Spanish)
- Liberating Voices (Swahili)
- LIBERATING VOICES (VIETNAMESE)
- Civic Ignorance / Anti-Patterns (English)
- Other
- Projects
- Community
- Digital Resources
- News
- About
- Contact
Testing Eliberate
Submitted by elemunjeli on Wed, 2013-02-13 11:18
I've been writing the logic code for Elib but as I progress, it's difficult to test since a meeting would typically have at least three members: a chair, one to motion, and one to second in order to be successful. Testing this manually is disorganized and tedious. I won't be able to tell whether the error is the machine, the user, or the code if I don't have automated testing for the simply the code.
So I've spent time to work out a complex unit test for meeting process that will run three instances. But that is taking some time. Definitely, the benefit is once I have that I can run hundreds of tests very quickly the way I have with the database IO. I really don't want to do it another way but it is going to hang up the user testing I think.
Wrote up some RROO basics for CIRAL.