понедельник, 27 февраля 2012 г.

#Faking #Testing

Вредные советы от Григория Остера Бена Симо.

Бен Симо (он же @QualityFrog) последние несколько дней жжет глаголом в твиттере.
Самые свежие новости можно найти по такому запросу.
Материалы, по утверждениям Бена, добыты следующим образом:
Go to Google or Bing and search for "Software Testing Best Practices" #Faking #Testing #ProTip #JustReadThis
Т.к. твиттер имеет свойство терять старые твитты и очень плохо искать не очень старые, то, считаю, надо сохранить для истории:
  • Expected results should not have any ambiguity. To remove ambiguity, reject reality and substitute a model. #Faking #Testing #ProTip
  • When automate test, you must make list of everything the automation does NOT do. #Faking #Testing #ProTip #TrueStory #ToInfinityAndBeyond
  • In software QA, make user agree to requirement as soon as possible . Then when customer not happy, blame customer. #Faking #Testing #ProTip
  • Most important in software QA is requirements freeze. QA must protect everything & everyone from change & learning. #Faking #Testing #ProTip
  • It doesn't matter if your best practices are best, or even good. They just need to be documented and enforced. #Faking #Testing #ProTip
  • No one is to share anything with anyone that may be perceived to be in conflict with the directive to automate everything. #Faking #Testing
  • There shall be no more talk of Exploratory Testing. We must achieve 100% automation. #Faking #Testing
  • "Economics of software #testing is to determine and predict the defects early by using predictable models..." #Faking #Unicorns
  • "Psychology of software #testing is to destructively test the application... sometimes called as the third vision." #Faking #Unicorns
  • A good set of test cases evaluatea "EVERY POSSIBLE permutation & combination of a program". Test it all! #Faking #Testing #Intractable
  • Good vibrations? "The vibration sensitivity of the software is one of the critical aspect of dynamic testing." #Faking #Testing #WTF
  • "Automated end-to-end testing is always better than manual testing." #Faking #Testing #Clueless
  • "Automated #testing has many advantages & benefits, incl the faster introduction of new functionalities and other related purposes." #Faking
  • "Manual tests could not have proper order and in many cases disorganized." #Faking #Testing #ProTip
  • "you should note that it is possible that the software will become confused and misled" #Faking #Testing #LMAO #WTF
  • "The vibration sensitivity of the software is one of the critical aspect of dynamic testing." #Faking #Testing #LMAO #WTF
  • "Dynamic tests ensure that software will function...right through its life cycle...at the user’s end." #Faking #Testing #Clueless
  • Dynamic #testing requires "a wide range of spectrum tools & equipments like analyzers, different sensors, & shakers" #Faking #Clueless #LMAO
  • "In real life, a 100% avg #testing effectiveness is not attainable, 100% can be achieved for a day or 2, but not for several days.." #Faking
  • "Through mutation #testing, it can be determined, if..testing methods used..were appropriate & adequate to ensure product quality." #Faking
  • Smoke #Testing "can expel all those software applications that lack the potential to reach the market." #Faking #ProTip #LMAO 
  • "when..software..fails, then you can safely assume that it is indeed a failure and you just cannot proceed further on #testing." #faking 
  • "no need for the tester to know how...process flows, he only needs to know if...software does what it is supposed to do" #Faking #Testing 
  • "according to Microsoft...smoke #testing defines...ascertaining or validating code changes before...introduced into...source tree." #Faking 
  • "Test cases form the major reasons why white box testing is so effective." #Faking #Testing 
  • In addition to change detection, white box "regression #testing will also uncover loopholes and vulnerabilities in the system" #Faking 
  • "white box #testing is a comprehensive test that leads to the development of a standard, fail-proof & complete software application" #Faking 
  • "main goal of any sw #testing is to ensure usefulness of a system against malicious hacker attacks or regular software problems." #faking 
  • Users love compilers. Give that user a compiler. "user need to have both a compiler and a computer to do...sanity #testing." #Faking #ProTip 
  • "Sanity #testing is very easy to perform. It is not complicated too. Just test it to check if it can produce the desired output." #Faking 
  • Sanity #testing is bad because "developers would not know how to fix any bugs or errors in sanity testing." #Faking #Testing #ProTip 
  • "Sanity #testing will not let software developers go deep into the software's problem in case any is encountered." #Faking #ProTip 
  • "In a scripted test, you should perform and document the whole testing process, regardless of the previous results" #Faking #Testing #ProTip 
  • Exploratory #testing is bad because it requires tester "who is willing to learn about the product". #Faking #Testing #ProTip #JustReadThis 
  • Documentation written before testing provides solid proofs that testers can provide to management. #Faking #Testing #ProTip #JustReadThis 
  • Exploratory #testing is bad because lack of documentation requires discussion of problems with team members. #Faking #ProTip #JustReadThis 
  • Exploratory #testing is bad because it "may require the services of skilled testers". #Faking #Testing #ProTip #JustReadThis 
  • Exploratory testing is best suited for post-production-deployment testing, when there is little time. #Faking #Testing #ProTip #JustReadThis 
  • There is no place for learning in testing. Learning during testing suggests incompetence in test planning. #Faking #Testing #ProTip 
  • Results reported by test automation provide more accurate interpretation of testing outcomes. #Faking #Testing #ProTip #JustReadThis 
  • "By definition, testing is a repetitive activity." #Faking #Testing #ProTip #JustReadThis 
  • PercentQuality = count(Testing.Defects) / (count(Testing.Defects) + count(Production.Defects)) #Faking #Testing #ProTip #JustReadThis 
  • Don't let programmers test their own code. They might fix defects without reporting them so they can be counted. #Faking #Testing #ProTip 
  • To measure quality, normalize defect counts from 1st 90 days after release per function point or LOC. #Faking #Testing #ProTip #JustReadThis 
  • Complying with QA process from the start will *remove* most of the defects. Enforce the process. #Faking #Testing #ProTip #JustReadThis 
  • Test cases & test coverage must also be determined 3 months before #testing starts. Reading documents takes time. #Faking #ProTip #TrueStory 
  • Requests for testing should be submitted to the QA department at least 3 months in advance. #Faking #Testing #ProTip #TrueStory 
  • Hold long meeting and have everyone remotely involved in a project review the detail of every test case before #testing. #Faking #ProTip 
  • Every test case and idea must be connected to a line item in a specification before it is tried. #Faking #Testing #ProTip 
  • Stop all testing if a smoke test fails. Your valuable time is best spent waiting on a new build. #Faking #Testing #ProTip #IJustReadThat 
  • Numbers and acronyms imply a scientific and systematic process; they increase credibility. Use as many as you can. #Faking #Testing #ProTip 
  • In Agile #testing, QA's role is process enforcement; ensure those wily developers comply with the documented CMMi processes. #Faking #ProTip 
  • Demand non-technical business people specify every technical detail of performance #testing before you start. #Faking #ProTip #TrueStory 
  • Create a committee to hash out the differences between smoke and sanity testing; then require everyone do both. #Faking #Testing #ProTip 
  • The larger the document, the less likely it is to get read. Make you test plans as huge as you can. #Faking #Testing #ProTip 
  • Make programmers meet stringent entry criteria b4 u test their stuff; delayed feedback forces them to think better. #Faking #Testing #ProTip 
  • If you pay peanuts, you get monkeys. Monkeys make good software testers. #Faking #Testing #ProTip #TrueStory 
  • Reject all bugs that aren't easily reproduced on the 1st attempt. Testers like to make s&!* up. #Faking #Testing #ProTip #TrueStory 
  • The context is testing. If you are testing, there is one best way. Hire an expert to show you the way. #Faking #Testing #ProTip #TrueStory 
  • To save time, toss out test cases for features expected to work; what should not be broken doesn't need #testing. #Faking #ProTip #TrueStory 
  • "We have no budget for it" is good enough reason for not #testing well. Theres no need to warn stakeholders of the risk. #Faking #ProTip 
  • Software licenses don't apply to #testing. 50 people can share 1 MSDN license if they all use same test lab. #Faking #DontTryThis #TrueStory 
  • If any test case is difficult or costly to automate or execute manually, consider it passed and move on. #Faking #Testing #ProTip #TrueStory 
  • In contracted software development, involve your company and client attorneys in every bug fix decision. #Faking #Testing #ProTip #TrueStory 
  • Don't upset management or auditors. Keep off-the-books bug lists for those inside your circle of trust. #Faking #Testing #ProTip #TrueStory 
  • Reward QA managers with bonuses based on % money saved by outsourcing and % time saved by automation. #Faking #Testing #ProTip #TrueStory 
  • Reward high test case execution counts. This discourages wasting time investigating and reporting bugs. #Faking #Testing #ProTip #TrueStory 
  • Hire QA managers who don't understand software. Then feed them folklore. Ignorance makes them easier to manipulate. #Faking #Testing #ProTip 
  • If there is any ambiguity in requirement documents, say "I can't test that!" and demand more documentation. #Faking #Testing #ProTip 
  • QA knows best. Every bug suspect must be fixed before the next release. Ain't nobody happy until QA is happy. #Faking #Testing #ProTip 
  • Count your test cases. Count them one by one. It is the best way to measure the good you've done. #Faking #Testing #ProTip 
  • Value testing artifacts over useful information; document production is easier to confirm and quantify. #Faking #Testing #ProTip 
  • When management demands n% of tests be automated, toss out manual tests to increase % automated. #Faking #Testing #ProTip #TrueStory 
  • If automated test script fails, comment out asserts until it works. #Faking #Testing #ProTip #TrueStory 
  • Testing requires no domain knowledge; only one week of test tool training is needed. #Faking #Testing #ProTip 
  • For better test coverage, automate existing test cases & run them continuously;whether the software changes or not. #Faking #Testing #ProTip 
  • QA must keep all on the path defined @ project start--the point of greatest ignorance. Quality is staying on path. #Faking #Testing #ProTip 
  • QA and development are natural enemies. Feed the animosity to keep everyone doing their best work. #Faking #Testing #ProTip 
  • It is best to require testers create detailed written bug reports for every suspect bug they encounter. #Faking #Testing #ProTip #TrueStory 
  • Don't include testers in project planning. They will only slow down progress. #Faking #Testing #ProTip #TrueStory 
  • Avoid putting asserts in your test automation. Asserts make tests run slower & less resistant to change. #Faking #Testing #ProTip #TrueStory 
  • When you test, only confirm that the software can do what it should do. Don't be concerned w what it should not do. #Faking #Testing #ProTip 
  • Spend a small fortune on big process-enforcing tools and you can then hire the cheapest commodity people available. #Faking #Testing #ProTip 
  • Always use document templates. They make it easier to create content-poor documents that impress. #Faking #Testing #ProTip 
  • Make others sign-off on your test plan as early as possible. Then blame those who accepted the doc when your #testing fails. #Faking #ProTip 
  • Make release decisions based on scores generated from counts of test case executions and bugs. #Faking #Testing #ProTip #TrueStory 
  • Bug counts are the best indicator of tester value. Reward big bug counts to encourage better #testing. #Faking #ProTio 
  • Demand zero ambiguity. Force others to document every detail; then they'll have no time to build things to test. #Faking #Testing #ProTip 
  • Easy certification brings respect. Nothing demonstrates your competence in #testing better than a multiple-false test. #Faking #ProTip 
  • Stop logging bugs; then use reduction in logged bug count as proof that process change improved quality. #Faking #Testing #ProTip #TrueStory 
  • Automate 95% of your testing with 5% of your resources. #Faking #Testing #ProTip 
  • Use the net change in defect count as a major factor in determining programmer and tester bonuses. #Faking #Testing #Protip #TrueStory 
  • Require programmers and testers create a flowchart for every unit and system test case. #Faking #Testing #Protip #TrueStory 
  • Test tool vendors are your best source of information about best practices in testing. Follow their lead. #Faking #Testing #Protip 
  • The testing phase should come long after the thinking phase. Testers are paid to execute scripts, not think. #Faking #Testing #ProTip 
  • And, whatever you do, don't let testers talk to customers. Nothing good can come of such promiscuous behavior. #Faking #Testing #ProTip 
  • Don't let testers communicate directly with programmers or business people; they only stir up trouble. #Faking #Testing #ProTip 
  • Identify and implement industry standard developer to tester ratios. The specifics of your context don't matter. #Faking #Testing #ProTip 
  • Stay positive. Require one positive thing be reported for every negative thing reported. #Faking #Testing #ProTip #TrueStory 
  • Save testing for the end. We don't need to know if we are on the right track until we get there. #Faking #Testing #ProTip 
  • Managers do not need to understand testing. As long as their people follow best practices, testing will be good. #Faking #Testing #ProTip 
  • Rush testing. Extreme time pressure gives testers opportunity and motivation to do their best work. #Faking #Testing #ProTip 
  • Test everything. And if you can't, claim you tested everything. After all, software is simple. #Faking #Testing #ProTip 
  • All relevant information is in the documents. Anything not explicitly documented is scope creep & is to be ignored. #Faking #Testing #ProTip 
  • Reward compliance with procedure over doing the wise thing. People hired for their minds should not be trusted. #Faking #Testing #ProTip 
  • Value consistency in testing above all else. Deviating from scripts leads to discovery that impacts schedule. #Faking #Testing #ProTip 
  • Reward quantity over quality. Counting is the foundation of evidence-based decision making. #Faking #Testing #ProTip 
  • Make bug reporting as detailed and tedious as possible. It helps filter and throttle the flow of information. #Faking #Testing #ProTip

2 комментария: