<p style="text-align: center;"> <img width="350" height="222" src="./Documentos/crash_test_2cv_gvsig-6asjornadas/" alt="" /> </p><p> </p><p>As you probably know, in the occasion of the 6th gvSIG International Conference it will be held a CodeSprint in which a group of developers will work intensively on fixing bugs.</p><p>The people in charge of the Testing Area of gvSIG thought that it would be a good idea to held a similar event called BugSprint, in which a group of users meet for test the application and feed the CodeSprint list of errors to be fixed with all the errors found on it. This would link the work done by both users and developers communities.</p><p><strong>The BugSprint goals are:</strong></p><p>- Promote the participation of the users community in testing.</p><p>- Show some testing methods used at gvSIG.</p><p>- Show best practices in:</p><p>    - How to delimit the cause of an error.</p><p>    - How to know if an error has already been reported.</p><p>    - How to open an issue in the bugTracker.</p><p><strong>¿When?</strong></p><p>On Tuesday November 29th 2010 (two days before the Conference) at 4pm. It’ll last about 4 hours although it’ll depend on your enthusiasm.</p><p>¿Where?</p><p>Central building of the Conselleria of Infraestructures and Transport in Valencia (Av. Blasco Ibáñez 50). Meeting room of the 6th floor.</p><p><strong>¿How to participate?</strong></p><p>Those who are interested should send an email to mmadrid [at] gvsig [dot] com. Each participant must bring its own laptop.</p><p><strong>Agenda:</strong></p><p>1. Introduction</p><p>    - Testing methods used at gvSIG.</p><p>    - Tools to be used.</p><p>    - Methodology.</p><p>2. Let’s test together!</p><p>3. Setting the priority to the open issues.</p><p> </p> <p style="text-align: center;"><strong><a href="http://www.ai2.upv.es/es/index.php"><br /></a></strong></p>