1. It's good to define exactly what we want to happen in various test cases. Either we can get consensus ("yeah, that's how it should turn out!") or decide that there's no clear answer. Both results add valuable information to the process.
2. We have examples to compare the actual Code of Conduct against to decide whether it achieves the results we want.
I'm not directly related to PyCon in any way other than as a happy attendee. As of this moment, I have no support (official or otherwise) for this project. I just think it could be a useful tool and an interesting exercise. Please jump in if you agree!
PS: The syntax is awful. I'm keenly aware of that, but I'm not aware of other testing frameworks for English documents and I'm making it up as I go along.
The idea is that:
1. It's good to define exactly what we want to happen in various test cases. Either we can get consensus ("yeah, that's how it should turn out!") or decide that there's no clear answer. Both results add valuable information to the process. 2. We have examples to compare the actual Code of Conduct against to decide whether it achieves the results we want.
I'm not directly related to PyCon in any way other than as a happy attendee. As of this moment, I have no support (official or otherwise) for this project. I just think it could be a useful tool and an interesting exercise. Please jump in if you agree!
PS: The syntax is awful. I'm keenly aware of that, but I'm not aware of other testing frameworks for English documents and I'm making it up as I go along.