以下为二维表信息
//统计严重等级Bug
SELECT severity,count(severity) FROM `bf_bugview` where product_id=476 GROUP BY severity
//统计创建者Bug
SELECT created_by_name,count(created_by_name) as count FROM `bf_bugview` where product_id=476 GROUP BY created_by_name ORDER BY count ASC
//统计解决者Bug
SELECT resolved_by_name,count(resolved_by_name) as count FROM `bf_bugview` where product_id=476 GROUP BY resolved_by_name ORDER BY count ASC
//统计各个版本Bug
select bf_add.version version,count(*) from bf_bug_info as b_info join bf_addonbug_476 as bf_add on (bf_add.bug_id=b_info.id) WHERE b_info.product_id = 476 GROUP BY version
//统计每一轮的新引入Bug
select bf_add.version,count(*) from bf_bug_info as b_info join bf_addonbug_476 as bf_add on (bf_add.bug_id=b_info.id) WHERE b_info.product_id = 476 and b_info.newly_bug= '是' GROUP BY bf_add.version
//统计每一轮的漏测Bug
select bf_add.version,count(*) from bf_bug_info as b_info join bf_addonbug_476 as bf_add on (bf_add.bug_id=b_info.id) WHERE b_info.product_id = 476 and b_info.missing_bug= '是' GROUP BY bf_add.version
//统计每一轮激活Bug
select bf_add.version,count(*) from bf_bug_info as b_info join bf_addonbug_476 as bf_add on (bf_add.bug_id=b_info.id) WHERE b_info.product_id = 476 and b_info.missing_bug= '是' GROUP BY bf_add.version
//统计每一轮的用例外Bug
select bf_add.version,count(*) from bf_bug_info as b_info join bf_addonbug_476 as bf_add on (bf_add.bug_id=b_info.id) WHERE b_info.product_id = 476 and b_info.case_bug= '是' GROUP BY bf_add.version
//Bug 类型分布
select
//统计每一轮的解决方案为已经修复和设计如此的Bug
select bf_add.version,count(*) from bf_bug_info as b_info join bf_addonbug_476 as bf_add on (bf_add.bug_id=b_info.id) WHERE b_info.product_id = 476 and (b_info.solution = 'Fixed' or b_info.solution='By Design') GROUP BY bf_add.version
//统计每个模块下的Bug信息(一直到所有模块节点)
select module_name,count(module_name) FROM bf_bugview where product_id = 476 GROUP BY module_name
//统计某个产品下有哪些模块
select b_pro_m.full_path_name,count(b_pro_m.full_path_name) from bf_product_module b_pro_m join bf_bug_info as b_info on (b_info.productmodule_id = b_pro_m.id) where b_info.product_id=476 GROUP BY b_pro_m.full_path_name
以下为三维表信息
//统计模块下的Bug信息
select bf_add.version version,count(bf_add.version) as '总数',count(bf_add_new.version) as '新引入',count(bf_add_miss.version) as '漏测',count(bf_add_testcase.version) as '用例外Bug',count(bf_add_fixed.version) as '已经修复或者设计如此'
from bf_bug_info as b_info join bf_addonbug_476 as bf_add on (bf_add.bug_id=b_info.id)
left join bf_addonbug_476 as bf_add_new on (bf_add_new.bug_id=b_info.id and b_info.newly_bug= '是')
left join bf_addonbug_476 as bf_add_miss on (bf_add_miss.bug_id=b_info.id and b_info.missing_bug= '是')
left join bf_addonbug_476 as bf_add_testcase on (bf_add_testcase.bug_id=b_info.id and b_info.case_bug= '是')
left join bf_addonbug_476 as bf_add_fixed on (bf_add_fixed.bug_id=b_info.id and (b_info.solution = 'Fixed' or b_info.solution='By Design'))
WHERE b_info.product_id = 476 GROUP BY version
select bf_add.version version,count(bf_add.version) as 'count1',count(bf_add_new.version) as '新引入',count(bf_add_miss.version) as '漏测',count(bf_add_testcase.version) as '用例外Bug',count(bf_add_fixed.version) as '已经修复或者设计如此',count(bf_add_reopen.version) as '激活'
from bf_bug_info as b_info join bf_addonbug_476 as bf_add on (bf_add.bug_id=b_info.id)
left join bf_addonbug_476 as bf_add_new on (bf_add_new.bug_id=b_info.id and b_info.newly_bug= '是')
left join bf_addonbug_476 as bf_add_miss on (bf_add_miss.bug_id=b_info.id and b_info.missing_bug= '是')
left join bf_addonbug_476 as bf_add_testcase on (bf_add_testcase.bug_id=b_info.id and b_info.case_bug= '是')
left join bf_addonbug_476 as bf_add_fixed on (bf_add_fixed.bug_id=b_info.id and (b_info.solution = 'Fixed' or b_info.solution='By Design'))
left join bf_addonbug_476 as bf_add_reopen on (bf_add_reopen.bug_id=b_info.id and b_info.reopen_count != '0')
WHERE b_info.product_id = 476 GROUP BY version
全局统计
//统计每个产品提交的Bug单数目
select bp.name,count(bp.name) count from bf_bug_info bf JOIN bf_product bp ON (bp.id=bf.product_id) where bf.created_at BETWEEN 20160101 AND 20161001 GROUP BY bp.name ORDER BY count DESC
//关键字title匹配
select bf.id,bf.title,bp.name from bf_bug_info bf join bf_product bp on (bp.id=bf.product_id) WHERE bf.created_at BETWEEN 20160101 AND 20161009 and bf.title like "DHCP%"
//按每个人员提交的Bug单
select bt.realname,count(*) count from bf_bug_info bf JOIN bf_test_user bt ON (bf.created_by =bt.id) WHERE bf.created_at BETWEEN 20100101 AND 20161009 GROUP BY bt.username ORDER BY bt.username DESC
//安装
- Jmeter实现登录bugfree、新建bug、解决bug脚本(抓包工具实现)
环境 Chrome jmeter3.1 fiddler4 win7 32位 Linux CentOs6.4 bugfree3.0.1 链接:http://pan.baidu.com/s/1gfHpbp ...
- (转)测试如何区别是前端的问题还是后台的bug
常常说到的一个IT项目,包括前端开发,后台开发,软件测试,架构,项目经理,产品需求.那么对于一位优秀的软件测试工程师来说,需要区分前端和后台的工作就显得尤为重要. - 什么是前端和后台 简而言之,前端 ...
- MapReduce -- 统计天气信息
示例 数据: -- :: 34c -- :: 36c -- :: 32c -- :: 37c -- :: 23c -- :: 45c -- :: 50c -- :: 33c -- :: 41c -- ...
- C# 后台添加Log信息
我们在做项目的时候,经常会使用到Log日志,今天分享一下如何在后台添加Log信息 创建一个写Log的方法: public void WriteLog(string Action) { try { st ...
- 关于Socket建立长连接遇到的bug信息
下面是本人在Socket连接的开发中遇到的bug总结 1."远程服务器关闭了Socket长连接'的错误信息 2.关于"kCFStreamNetworkServiceTypeVoIP ...
- HttpWebRequest调用WebService后台需要Session信息问题的解决办法
今天在用HttpWebRequest调用后台ASP.NET 的WebService方法时遇到了一个问题,后台的WebService方法里使用到了Session对象中的用户信息,而Session对象中的 ...
- C# 前台和后台POST提交信息的实现方法
一.系统A(官网)与系统B(第三方支付平台)数据交换的方式 1.1 页面浏览器方式:系统A以构造Form表单的方式,通过系统A客户的浏览器重定向到系统B(向系统B发送请求),B系统完成交易后,将交易 ...
- df -h统计的信息与du -sh不一致的原因(转)
有时候会遇到这样的问题:df -h统计一个目录,显示有约100M可用空间,使用了5G:而用du -sh统计该目录下的文件大小,却发现总共才占用了1G.也就是说,二者统计结果差距巨大. 例如: 1.df ...
- (二十五)后台开发-分类信息的curd -展示所有实现
案例1-分类信息的curd 步骤分析: 左边的dtree: 1.导入dtree.js 2.导入dtree.css 3.创建一个div 添加样式 class="dtree" 4.在d ...
随机推荐
- models的单表操作
orm创建数据库 from django.db import models # Create your models here. class Book(models.Model): name = mo ...
- 深入浅出SharePoint——常用的系统账号
NT AUTHORITY\Authenticated Users添加此用户后所有windows认证的ad用户都被授权.注意添加的时候如果搜索不到,可以直接输入Authenticated Users,然 ...
- August 08th 2017 Week 32nd Tuesday
The very essence of romance is uncertainty. 浪漫的精髓就在于它充满种种可能. Romance is the glamour that can turn th ...
- [COGS 0107][NOIP 2003] 传染病控制
107. [NOIP2003] 传染病控制 ★★★ 输入文件:epidemic.in 输出文件:epidemic.out 简单对比时间限制:1 s 内存限制:128 MB [问题背景] ...
- SuperSocket 介绍
一.总体介绍 SuperSocket 是一个轻量级的可扩展的 Socket 开发框架,由江振宇先生开发. 官方网站:http://www.supersocket.net/ SuperSocket具有如 ...
- Angular组件之间通讯
组件之间会有下列3种关系: 1. 父子关系 2. 兄弟关系 3. 没有直接关系 通常采用下列方式处理(某些方式是框架特有)组件间的通讯,如下: 1父子组件之间的交互(@Input/@Output/模板 ...
- 利用memcached实现分布式锁
一 需求场景: (1) 需要限制用户创建提现订单的频率:目的一是防止前端bug引起的用户重复提交:二是防止并发攻击绕过提现策略(第一次提现和第二次提现门槛可能不同). (2) 需要限制秒杀下同一用户 ...
- stylus的用法
参考链接:预处器的对比——Sass.LESS和Stylus http://www.w3cplus.com/css/sass-vs-less-vs-stylus-a-preprocessor-sho ...
- Spring(十)之自定义事件
编写自定义事件的简单流程如下: (1)编写CustomEvent.java package com.tutorialspoint; import org.springframework.context ...
- VC++获取一个GB级大文件的字节大小
常规的获得小文件(2.1GB以下)的字节大小可以使用ftell,函数 ftell 用于得到文件位置指针当前位置相对于文件首的偏移字节数.使用fseek函数后再调用函数ftell()就能非常容易地确定文 ...