home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Unit testing guidelines
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="TheTechnologist" data-source="post: 35612" data-attributes="member: 10987"><p>My point here is that doing the coverage of a codebase that has not been written with tests at all (and probably with very poor code coverage) means that you need to commit certain failing tests to show where work needs to be done (argument sanitation is a common example) and the progress done. If it's a new code base it's a different case, but asking for unit tests to all pass assumes you always commit your test at the same time as the code needed for the test to pass, and that's assuming someone that discover a bug and write a test with it would commit the modified code without necessarily knowing what he's doing.</p><p></p><p>Anyway, let's talk about that at a later point, after all i've never contributed back any of my changes from the branching i did on mediaportal so i shouldnt complain about anything at all.</p></blockquote><p></p>
[QUOTE="TheTechnologist, post: 35612, member: 10987"] My point here is that doing the coverage of a codebase that has not been written with tests at all (and probably with very poor code coverage) means that you need to commit certain failing tests to show where work needs to be done (argument sanitation is a common example) and the progress done. If it's a new code base it's a different case, but asking for unit tests to all pass assumes you always commit your test at the same time as the code needed for the test to pass, and that's assuming someone that discover a bug and write a test with it would commit the modified code without necessarily knowing what he's doing. Anyway, let's talk about that at a later point, after all i've never contributed back any of my changes from the branching i did on mediaportal so i shouldnt complain about anything at all. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Unit testing guidelines
Contact us
RSS
Top
Bottom