te')); return $arr; } /* 遍历用户所有主题 * @param $uid 用户ID * @param int $page 页数 * @param int $pagesize 每页记录条数 * @param bool $desc 排序方式 TRUE降序 FALSE升序 * @param string $key 返回的数组用那一列的值作为 key * @param array $col 查询哪些列 */ function thread_tid_find_by_uid($uid, $page = 1, $pagesize = 1000, $desc = TRUE, $key = 'tid', $col = array()) { if (empty($uid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('uid' => $uid), array('tid' => $orderby), $page, $pagesize, $key, $col); return $arr; } // 遍历栏目下tid 支持数组 $fid = array(1,2,3) function thread_tid_find_by_fid($fid, $page = 1, $pagesize = 1000, $desc = TRUE) { if (empty($fid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('fid' => $fid), array('tid' => $orderby), $page, $pagesize, 'tid', array('tid', 'verify_date')); return $arr; } function thread_tid_delete($tid) { if (empty($tid)) return FALSE; $r = thread_tid__delete(array('tid' => $tid)); return $r; } function thread_tid_count() { $n = thread_tid__count(); return $n; } // 统计用户主题数 大数量下严谨使用非主键统计 function thread_uid_count($uid) { $n = thread_tid__count(array('uid' => $uid)); return $n; } // 统计栏目主题数 大数量下严谨使用非主键统计 function thread_fid_count($fid) { $n = thread_tid__count(array('fid' => $fid)); return $n; } ?>laravel - Specific unit testing requirement - Stack Overflow

科技改变生活-雨落星辰 - 所有的伟大,都源于一个勇敢的开始

    最新消息：雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客
    你的位置： 首页>programmer>laravel - Specific unit testing requirement - Stack Overflow

    laravel - Specific unit testing requirement - Stack Overflow

    programmeradmin3浏览0评论

    I am attempting to make a custom upgrade of a project which is based on an old version of Laravel. Part of this upgrade will be updating it to the current version of Laravel.

    This project has no unit tests.

    I am writing tests for the project before upgrading as a means of reducing the risk of something being broken after the upgrade.

    Since this is a huge project writing 100% test coverage would be very time consuming so instead I want to write tests which only cover parts of the code which use Laravel functions ( its ok for more code to be covered as long as the Laravel function calls are all covered ) It is also only necessary for each Laravel call to be tested once By that I mean if one function in some class somewhere calls a Laravel function and is covered by tests then there is no need for tests to cover other pieces of code which call the exact same laravel function.

    My question is how can I make sure that I have achieved this?

    Things I have tried / considered....

    I am not aware of any code coverage reporting tool which shows you if any un-covered lines of code match an identical line of code which is covered.

    I considered using a extension for my IDE which shows code coverage within the IDE because this would enable me to open function declarations from the code and see if it has been covered - however this would be be helpful because that would only show if the underlying function has been covered as a result of it being run from somewhere - it would not prove it has been covered as a result of the project code calling it.

    与本文相关的文章

    发布评论

    评论列表(0)

    1. 暂无评论