46. Do you have a full-time software tester?
There is a full-time test. If the human hand is not enough, you can exchange the test. Don't test your own yourself.
47. Do you have a general plan to specify what to do and how to do?
This is Test Plan. Do you want to do performance testing? Do you want to do a USABILITY test? When do you start testing performance? What is the standard passing? What is the means, automatic or manual? These problems need to be answered with Test Plan.
48. Do you write Test Case first and then test it?
It should be. It should be designed before programming, first Test Case and then test. Of course, things are flexible. I sometimes make Test Case while doing the first pass. As for the first Test Case again, I don't like it, because I am not used to it, it is too trouble, as for others, try it.
49. Will you create test cases for various input combinations?
Don't, don't engage in border conditions. When the heart combination explosion. There are a lot of Test case tools to automatically generate a combination of various boundary conditions - but if you want to clear, do you have time to run so much Test Case.
50. Can your programmers see test cases?
want. Let DEV see TEST CASE. We are all come together for the same purpose: improve quality.
51. Do you have someone else to do any useful test?
To do this. I look at my own program interface, how to see it is pleasing. This is called aesthetic fatigue - it is not smelling for a long time. It is used to it.
52. Are you the expectation of automatic testing?
Don't expect too much. According to me, in addition to performance test, I still forget "automatic test", forget WinRunner and LoadRunner. For the status quo of domestic software test, it can only be "correctly" must pass. "
53. Does your performance test do all functions have been done?
can not be like this. Performance tests cannot be returned to a so-called "system test" phase. Early measurement, early death, early death.
54. Have you noticed the insecticide effect in the test?
Bug has anti-drug resistance, BUG is also. The new bug found is less and less normal. At this time, it is best to exchange the Tested Area, or use other tools and techniques, will find some new bugs.
55. Is there anyone in your project group to say the current overall quality of the product?
There is. When the boss asks this product, Test Lead / Manager should be responsible for answering.
56. Do you have a unit test?
Unit tests must be. However, there is no unit test, I have done a project that has no unit test, and it will be successful - it may be lucky, maybe everyone is the relationship of the family. Still, software engineering is very practical, very engineered, very flexible, some methods will be better than others in some cases, and vice versa.
57. Your programmer throws the wall after writing the code?
Badge. After writing a program, even if you don't do unit test, you should run a run. Although there are special testers, people who do developing are not doing it. Microsoft also has Test Release Document's statement, the program is too bad, the test has the right to kick it.
58. Are all functions in your program have input checks?
Don't. Although it is said that the input check is the point of Write Secure Code, do not do too much input check, the parameter passes between some internal functions do not have to check, save the efforts. The same reason, not necessarily written to all functions. It is enough to write some main.
59. Does the product have a unified error handling mechanism and an error interface? There is. It is best to have uniform error messages, and then each Error Message takes an error number. In this way, users can go to the error specific description and possible reasons of Error Number to User Manual, just like SQL Server errors. Similarly, ASP.NET also has a unified Exception process. You can refer to the Application Block.
60. Do you have a unified code writing norms?
There is. Code Convention, you can send it to everyone. Of course, if there is a FXCOP tool to check the code is better.
