Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
wshtrue
Yak Posting Veteran
74 Posts |
 Posted - 2005-06-08 : 23:28:57
|
| Hi Guys,I have one more question. In my company i think that developers don't do unit testing before moving it to QA so lot of time is wasted on those issues which we should not be covering if unit testing is done properly so i am not sure if this is the right form to ask help for this but thought of giving it a try and finding out from Good Senior Developers that if we have to make sure that Senior Developers have done unit testing and covered all the requirements then what should be the acceptance criteria.Is there any place from where i can get some sample form for acceptance criteria or anyone from your team can suggest me some of the things i should put it on form and give it to Developers and tell them that they need to check it when all options are covered and then only it should be send to QA. Its just an idea but I am not sure what options should be?What about you guys? When you send your code to QA so what are the things you make sure that you have covered.Do you guys have any sign off sheet something like that?Any help will be greatly appreciated.Thanks |
|
|
raclede
Posting Yak Master
180 Posts |
Posted - 2005-06-09 : 00:15:58
|
Well in our company, the dev guys develops, performs component and integration testings in the DEV before submitting to QA.. Before submitting to QA for Testing, developers are required to submit the Technical Specifications (Table Structures, Stored Proc etc.) and Test Plan. Test Plan is a document wherein the developer writes all scenario to all components of a program, what will the user do, the component/files to be test, the expected result, time of execution, reports if any, and in this document the Tester will based his/her testing.. After that if no bugs have been found they will create a rollout plan for production."If the automobile had followed the same development cycle as the computer, a Rolls-Royce would today cost $100, get a million miles per gallon, and explode once a year, killing everyone inside. " raclede |
 |
|
|
wshtrue
Yak Posting Veteran
74 Posts |
Posted - 2005-06-09 : 00:31:34
|
| Hello,Thanks for your reply but there is no test plan in my company.QA process is fine my question is if i want them to give me checklist then i need to give them sample of checklist that this is what they need to make sure that everything has been checked so what are the main issues which i should put on checklist sample.Hope i am clear.Thanks |
|
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2005-06-09 : 07:32:46
|
| In order to fast track the mechanical aspect of a CODE QA....(and not compliance with functional/technical specs per se), then you may wish to investigate (if using VB), something like VBLAW from http://www.visibleprogress.com, where you can apply good coding practices to your developers code before it goes near the testers. It'll help cut out the stupid sh*t, that slows down the test cycles, and over time will assist good (or at a minimum consistant) coding practices.There's a limited use demo version downloadable from that site, and it comes with sample 'rules' which can be adapted to your work environment.It allows QA sessions to concentrate on the quality of the code/adherance to spec rather than spending time identifying clashes with spelling guidelines.Re no Test Plans.....ooops!While a pain in the ass sometimes, having a list of tests to be executed does focus the mind of everybody (esp mgmt and users) on the o/s effort to be applied and the cost (and benefits) of pass/failure/skipping any functional areas. Our test plans would be quite basic, but having a formal list of passed tests does give a confidence boost when coming up to release dates. |
|
|
|
wshtrue
Yak Posting Veteran
74 Posts |
Posted - 2005-06-09 : 09:03:39
|
| Hi Guys,Thank you for your reponse but my company is using SQL server 2000 and C#. 60% of our time goes in doing unit testing so i was very tired and i told my manager that developers should give us some checklist with screenshots of results that they did unit testing but since i am not a senior level developer so was wondering what should be on checklist which should be given to QA so that we know that they really did unit tesing.I hope i am clear.Thanks |
|
|
|
|
|
|
|
|
Acceptance Criteria Form From Dev to QA