Search results

From CitconWiki
Jump to navigationJump to search

Page title matches

  • It's possible to write a test which achieves extremely high code coverage for a system yet doesn't test the system at all. ...duce that uncovered code ''may'' contain errors and '''not''' that covered code is error free.
    1 KB (180 words) - 02:58, 29 June 2008

Page text matches

  • It's possible to write a test which achieves extremely high code coverage for a system yet doesn't test the system at all. ...duce that uncovered code ''may'' contain errors and '''not''' that covered code is error free.
    1 KB (180 words) - 02:58, 29 June 2008
  • What kind of code metrics do you collect? * Coverage
    305 bytes (38 words) - 10:39, 15 August 2008
  • We all want to achieve a high level of coverage to give us confidence in the code, but at what levels should we focus our efforts, and how much? ...can have detrimental effects. Yet, taking the time too get extensive code coverage at all levels may be costly and cause delayed releases and/or sales.
    530 bytes (96 words) - 04:51, 28 June 2009
  • ...ssion right up the other end of the spectrum, about achieving '''100% test coverage''', what that means exactly and whether attempting such a thing is even wis == A Tighter Definition of Code Coverage Numbers ==
    3 KB (541 words) - 09:05, 2 April 2008
  • ..., developing [http://www.atlassian.com/software/clover/ Clover2], the code coverage and test insight tool for Java.
    161 bytes (24 words) - 23:33, 18 June 2008
  • David Soul is a sales engineer for the Bamboo CI server and Clover code coverage tools from Atlassian.
    102 bytes (18 words) - 22:49, 25 June 2009
  • == Your Code as a Crime Scene == [https://pragprog.com/book/atcrime/your-code-as-a-crime-scene The book at pragmatic programmers]
    1 KB (243 words) - 18:19, 27 May 2019
  • ...in tools and processes that we can use to expand our automation, eg. code coverage, automatic documentation.
    280 bytes (42 words) - 06:33, 26 June 2008
  • #[[Does high Code Coverage mean high test quality?]] #[[Does high Code Coverage mean high test quality?]]
    752 bytes (86 words) - 17:05, 6 July 2008
  • Sonar - publishes Code Coverage and Technical Debt
    477 bytes (63 words) - 10:30, 4 October 2015
  • cyclomatic complexity - people that are very familiar with the code will notice outlayers - "why is that little thing so complicated?" code coverage - worthless. trend could be interesting
    998 bytes (157 words) - 13:16, 17 April 2010
  • == Coverage == ...ive metric (i.e.: if there is 0% coverage, we can say for a fact that that code is definitely NOT tested)
    1 KB (210 words) - 04:47, 8 October 2013
  • ...ng a metric that "measures code health" is not the same as one that "finds code sickness", and I'm more interested (for the moment) in the later. ...art the discussion I introduced CRAP4J, a free tool that tries to identify code that, if you had to inherit it, you'd probably declare as crappy. The purpo
    4 KB (596 words) - 05:27, 10 September 2012
  • ''mental note, for macetw, we need more code-literature in our bathroom'' ** Would affect code coverage numbers
    1 KB (198 words) - 10:54, 24 August 2013
  • Adding code coverage to every build * % of code
    3 KB (472 words) - 07:25, 19 September 2009
  • Jester is a mutation test tool that change the code. If the tests still pass, then it means that tests are missing. ...g thing is that it is running on the classes that already have a good code coverage.
    2 KB (328 words) - 00:12, 25 October 2010
  • - Code Duplication - Code Coverage
    2 KB (245 words) - 21:05, 9 April 2008
  • Someone asked "why do you not measure coverage?". I took this personal and will put it back on the agenda. I also want measure complexity of our C++ code as part of the automated build.
    640 bytes (112 words) - 02:51, 28 June 2008
  • * Improve visibility and assurance of code quality * Code reviews
    2 KB (327 words) - 14:17, 22 August 2008
  • One of the guys use visualises to track code quality. Showing where problems are in the code.
    4 KB (602 words) - 17:10, 6 July 2008
  • == Tracking Code Quality == ...A tag cloud containing every class that exposes those which have low test coverage but high cyclomatic complexity
    2 KB (301 words) - 14:55, 29 June 2008
  • UI test first if low or 0% test coverage? Code coverage (can a tool tell us what needs to be run, or does it need to be manually ta
    3 KB (619 words) - 12:13, 24 August 2013
  • == Untesttable Code? Bullshit == 2. Just enough code to make the test pass
    4 KB (609 words) - 22:27, 5 August 2016
  • TDD principles: No coding until we have a broken test made. Only code until the test passes, no more. ...superflous code, beyond what is needed to pass the test, as it has no test coverage.
    2 KB (390 words) - 02:04, 27 June 2010
  • *** Allows juice scripts to be mapped to source code changes ...suggest the best juice scripts to run to get the best possible coverage of code
    2 KB (320 words) - 04:11, 1 December 2010
  • What are the code quality metrics that we can use for ...ode coverage to management, use only a part of the codebase. Show them the coverage of the most important features.
    4 KB (636 words) - 10:31, 22 October 2012
  • #[[What Is After 100 Pct Coverage And Functional Tests]] #[[Code Metrics]]
    1 KB (196 words) - 12:28, 1 April 2008
  • Without TDD, you write bugs faster. With TDD, you write code faster. With TDD, you write *working* code faster. That's a better definition of TDD
    4 KB (641 words) - 02:26, 20 October 2012
  • ...k, can we measure customer-revenue outcomes from how we are committing our code? Feedback of code
    4 KB (601 words) - 07:25, 27 August 2013
  • #[[Code Coverage]] |[[Code Coverage]]
    2 KB (264 words) - 18:58, 10 May 2012
  • * If the test fails and you change the code, the it is a GOOD test Microsoft Reverse Code Coverage tool?
    2 KB (369 words) - 01:12, 12 September 2015
  • ...ness model is captured in the wiki (whatever format) and at least 80% code coverage by unit tests with tools. - sustainable pace by clean code/code coverage/complexity
    4 KB (605 words) - 23:57, 23 September 2009
  • * Source code management integration ** Coverage metrics
    3 KB (476 words) - 19:29, 5 August 2007
  • ==Code== ...valuable feedback for tests and code alike. (Ideally each mutation of the code will be 'killed' by exactly one test specifying that specific behaviour.) S
    5 KB (777 words) - 07:40, 18 September 2015
  • • Collect code coverage • Identify problem code/classes
    3 KB (481 words) - 05:29, 10 September 2012
  • * Realizing code doesn't exist in a vacuum, traceability into what make things break, we can * Code coverage is not per line, but per logic piece within a line
    2 KB (338 words) - 06:35, 27 August 2013
  • ...an 18 month project. (Last 10-12 months code & fix, and you can't estimate code & fix.) ...utomated testing with your build/check-in process so you can see test case coverage.
    3 KB (569 words) - 07:20, 30 June 2010
  • 5. start measuring code coverage
    2 KB (256 words) - 05:01, 12 September 2015
  • ...nd a correspomnding arguments class, and use those objects from inside the code to access the database), which would highlight such discrepancies at compil ...question about intelligent characteristic test data generation to provide coverage in legacy systems, similar to the way agitar's product works in the java sp
    3 KB (562 words) - 11:47, 10 November 2010
  • Not poss to automate everything... trade off of coverage. We do code quicly, cheaply, reliably... pick any two.
    5 KB (739 words) - 20:12, 25 June 2010
  • ...anything serious. False sense of being complete. Don't have complete code coverage that you need. Need to do more comprehensive testing. ...might need to refactor your automated test. May need to reuse some of the code that you've written.
    8 KB (1,340 words) - 15:10, 22 September 2012
  • Co-workers checked in code that didn't work. Code should compile before you check it in. Read Scott Adams, "Goals are for los ...number of test cases, and take a snapshot of current state. New version of code on the other side, and then compare the test results according to the DOM.
    10 KB (1,811 words) - 15:01, 22 September 2012
  • [[What Is After 100 Pct Coverage And Functional Tests]] -- [[David O'Hara]] [[Code Metrics]] -- [[Paul Holser]], [[Eric Pugh]], [[Vandana Shah]], [[Harlan Woo
    7 KB (1,012 words) - 05:29, 10 September 2012