Intercommunication between Design, Development and Testing department <br /><br /><br />Document Name:&nbsp;&nbsp; &nbsp;Intercommunication between departments. <br />Prepared by:&nbsp;&nbsp; &nbsp;Reena Athalye<br /><br /><br />Version History:<br />Version&nbsp;&nbsp; &nbsp;Date (DD/MM/YYYY)&nbsp;&nbsp; &nbsp;Comments<br />1.0&nbsp;&nbsp; &nbsp;29-06-2006&nbsp;&nbsp; &nbsp;Department intercommunication guidelines.<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />Working of Testing Department&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;<br /><br />For good functioning of this department, the testers need to be introduced in the process from the very beginning. &nbsp;<br />The testers will perform testing on the applications that are sent to them from the Development Department. All the defects will be logged in a Defect Management Tool – Mantis for projects developed in-house. Every developer has and will have a login for Mantis. Any communication on a defect will be done through Mantis.<br />For outsourced projects, excel sheets will be maintained.<br /><br />Testing Schedule:<br />1.&nbsp;&nbsp; &nbsp;The time estimate for testing will be defined by the Testing dept head and the project coordinator mutually.&nbsp; &nbsp;<br />2.&nbsp;&nbsp; &nbsp;Any change in the functionality will result in change of testing schedule.<br /><br />Testing for Development:<br />1.&nbsp;&nbsp; &nbsp;While forwarding a testing request, all the details related to the project and specifications (if any) should be sent. <br />2.&nbsp;&nbsp; &nbsp;All defects will be logged and updated in Mantis with snap shots wherever necessary for in-house projects. For outsourced projects they will be listed in excel sheets.<br />3.&nbsp;&nbsp; &nbsp;If testing is not started on time and results in delay, then it will be the tester responsibility to cope with the schedule.<br />4.&nbsp;&nbsp; &nbsp;It is the responsibility of the tester to write the defect in a way which can be easily understood by anyone.<br />5.&nbsp;&nbsp; &nbsp;Testers will start regression testing of only those issues whose status is seen as ‘resolved’ in Mantis. Similarly for excel sheets.<br />6.&nbsp;&nbsp; &nbsp;The developers will be expected to add notes in Mantis if necessary. Similarly for excel sheets.<br />7.&nbsp;&nbsp; &nbsp;Any change in functionality should be also communicated to the testers.<br />8.&nbsp;&nbsp; &nbsp;Changes should be uploaded before the respective issues are resolved in Mantis.<br />9.&nbsp;&nbsp; &nbsp;Unit Testing should be done by developers without which testing will not be done by the testing dept.<br />10.&nbsp;&nbsp; &nbsp;If too many defects are found and results in delay, it would be the developer’s responsibility to later cope with the schedule.<br />11.&nbsp;&nbsp; &nbsp;In case of any design change, the templates will be first sent for testing.<br />12.&nbsp;&nbsp; &nbsp;When a module is sent for testing, no changes will be made in that module by the developers. Any change will be sent as new request for testing.<br /><br />Testing for Designing:<br />1.&nbsp;&nbsp; &nbsp;While forwarding a testing request, all the details related to the project and specifications (if any) should be sent. <br />2.&nbsp;&nbsp; &nbsp;All defects will be logged and updated in Mantis with snap shots wherever necessary for in-house projects. For outsourced projects they will be listed in excel sheets.<br />3.&nbsp;&nbsp; &nbsp;If testing is not started on time and results in delay, then it will be the tester responsibility to cope with the schedule.<br />4.&nbsp;&nbsp; &nbsp;Any special requirements like browser, resolution etc should be conveyed to the tester in the request for testing.<br />5.&nbsp;&nbsp; &nbsp;Any change in the design should be communicated to the tester even if the website is already uploaded.<br />6.&nbsp;&nbsp; &nbsp;After uploading the website, it should be re-sent for testing.<br />7.&nbsp;&nbsp; &nbsp;All the defects should be updated through Mantis.<br />8.&nbsp;&nbsp; &nbsp;Testers will start regression testing of only those issues whose status is seen as ‘resolved’ in Mantis.<br />9.&nbsp;&nbsp; &nbsp;If too many defects are found and results in delay, it would be the designer’s responsibility to later cope with schedule.<br /><br /><br />Inter Departmental Communication&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;<br /><br /><br />Development/Designing to Testing:<br />Every request for testing will be sent through e-mail by the development dept to the testing dept.<br /><br />The mail should include all the details like:<br />a.&nbsp;&nbsp; &nbsp;URL’s<br />b.&nbsp;&nbsp; &nbsp;Username and passwords<br />c.&nbsp;&nbsp; &nbsp;Reason for sending it to testing. Ex: change in functionality, regression testing, and first time testing.<br />d.&nbsp;&nbsp; &nbsp;Any other things that the developer would like the tester to know.<br /><br />When the developer will send the project for testing for the first time he/she will send it ‘To’ - Testing Head.<br />&nbsp;&nbsp; &nbsp; ‘CC’ - Development/Design Head<br />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;Project Coordinator&nbsp;&nbsp; &nbsp;<br />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;Business Development Head<br />Testing Head will assign the Project to a tester.<br />&nbsp;To - Tester<br />&nbsp;CC - Development/Design Head<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Project Coordinator&nbsp;&nbsp; &nbsp;<br />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;<br /><br />Testing to Development/Design:<br />When all defects for a module or application are resolved and closed, the tester working on the project will send a testing completed mail.<br /><br />The following people should be marked in ‘To’ – Developer<br /><br />The following people should be marked in ‘CC’ – Testing Head<br />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Development/Design Head<br />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Project Coordinator&nbsp;&nbsp; &nbsp;<br />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Business Development Head<br /><br />Project Coordinator to Testing:<br />The project coordinator will send an email if any defects are found by him/her.<br /><br />The following people should be marked in ‘To’ – Tester <br /><br />The following people should be marked in ‘CC’ – <br />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Testing Head<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Development/Design Head<br />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Developer/Designer <br />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Business Development Head<br /><br />Project Coordinator to Development/Design and Testing:<br />The project coordinator will send an email regarding the client feedback and which also might include any changes suggested by the client.<br /><br />The following people should be marked in ‘To’ – Development/Design Head<br /><br />The following people should be marked in ‘CC’ – Testing Head<br />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Developer/Designer <br />&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Business Development Head<br /><br />*All documents send across within the department or to the client should have Properties correctly added in it.<br />In the menubar click on File-&gt;Properties-&gt;Summary<br /><br />&nbsp;<br /><br />