世界的瞭望哨

“认识自己 认识世界”

Http接口测试框架架构设想

序言

按照惯例,谷歌了几个来回,没找到合适的开源框架

于是乎,自己折腾一个!?

框架要点

  1. 是否易于上手,学习和迁移成本要低,要不然潜在用户手头上一堆旧用例怎么愿意换框架呢
  2. 可以以尽量少的代码写出丰富用例来,这一点我现在认为是非常重要的;代码越少,用例本身越清晰明了,写得时候轻松自如,code review及以后维护起来也是大大的方便;这种精简,可以通过框架提供简单优雅的API实现,也可以通过设计一个灵活而不失强大的数据驱动模型实现,也可以通过合理封装被测试产品的业务逻辑实现;实践表明,写测试用例的时候,是非常容易出现冗余代码的,如何消除这种冗余,是个关键问题
  3. 框架本身的代码也要精简,原理基本同上
  4. 框架要灵活,不能因为框架而把大家写用例的思路限制住;产品各不相同,业务千差万别,测试人员也各具特长,写出来的用例大一统,不现实,也不该
  5. 一个比较激进的设想,使用Ruby来架构及写用例;与Java相较,Ruby天然具有灵活性和精简性;但是要迁移语言体系,风险与收益共存

框架模块

  1. HttpClient封装,可自己封装,也可采用优秀库
  2. 断言封装,可自己封装,也可采用优秀库,例如:直接使用TestNg
  3. 测试数据组织形式,xml?excel?写在代码里?
  4. 业务逻辑相关封装
  5. 用例组织与执行,不出意外,采用现成框架即可,例如:TestNg

其中第三第四点很难把握,直接关系到大家如何设计和架构测试用例,以及是否方便使用这个框架写用例和维护用例

尤其是第四点,倾向于由实际用例编写人自主设计

小调查

在周边人群中进行了一次小调查,如图所示

小调查

尝试

利用业余时间在使用Ruby进行折腾,请看这里

Ruby学习系列 - 基础知识 - Hash

序言

这部分讲Hash,取材于Ruby core API,加以归纳整理,便于记忆

赋值

1
2
3
4
h = { "a" => 100, "b" => 200 }
h["a"] = 9
h["c"] = 4
h   #=> {"a"=>9, "b"=>200, "c"=>4}

取值

1
2
3
h = { "a" => 100, "b" => 200 }
h["a"]   #=> 100
h["c"]   #=> nil
1
2
3
4
h = { "a" => 100, "b" => 200, "c" => 300, "d" => 300 }
h.key(200)   #=> "b"
h.key(300)   #=> "c"
h.key(999)   #=> nil

运算

1
2
3
4
5
6
h1 = { "a" => 100, "b" => 200 }
h2 = { "b" => 254, "c" => 300 }
h1.merge(h2)   #=> {"a"=>100, "b"=>254, "c"=>300}
h1.merge(h2){|key, old_val, new_val| new_val - old_val}
               #=> {"a"=>100, "b"=>54,  "c"=>300}
h1             #=> {"a"=>100, "b"=>200}

增减

1
2
3
h = { "a" => 100, "b" => 200 }
h.delete("a")                              #=> 100
h.delete("z")                              #=> nil
1
2
h = { "a" => 100, "b" => 200, "c" => 300 }
h.delete_if {|key, value| key >= "b" }   #=> {"a"=>100}

reject! is equivalent to Hash#delete_if, but returns nil if no changes were made.

统计与查询

1
{}.empty?   #=> true
1
2
3
h = { "a" => 100, "b" => 200 }
h.has_key?("a")   #=> true
h.has_key?("z")   #=> false
1
2
3
h = { "a" => 100, "b" => 200 }
h.has_value?(100)   #=> true
h.has_value?(999)   #=> false
1
2
h = { "a" => 100, "b" => 200, "c" => 300, "d" => 400 }
h.keys   #=> ["a", "b", "c", "d"]
1
2
h = { "a" => 100, "b" => 200, "c" => 300 }
h.values   #=> [100, 200, 300]
1
2
3
4
h = { "d" => 100, "a" => 200, "v" => 300, "e" => 400 }
h.length        #=> 4
h.delete("a")   #=> 200
h.length        #=> 3
1
2
3
h = { "a" => 100, "b" => 200, "c" => 300 }
h.select {|k,v| k > "a"}  #=> {"b" => 200, "c" => 300}
h.select {|k,v| v < 200}  #=> {"a" => 100}

其它

1
2
h = { "a" => 100, "b" => 200 }
h.each {|key, value| puts "#{key} is #{value}" }
1
2
h = { "a" => 100, "b" => 200 }
h.each_key {|key| puts key }
1
2
h = { "a" => 100, "b" => 200 }
h.each_value {|value| puts value }

小结

以上为不完全统计,后续调整

瓜熟才可蒂落

本文算是最近工作中的一些感悟与吐槽

话说本人是互联网行业QA一枚,精确一点叫测试开发,测试中的开发(很遗憾不是战斗机==!)

也许大家在用脚本执行测试,在用Jenkins执行自动用例,在用testlink管理用例,在用JIRA管理Bug,etc。但终有一天,随着业务的发展,一个集中而不失灵活,强大而不失轻巧的(测试)平台必将出现。我相信,这样一个平台,可以而且应该:

  1. 符合本公司/部门的业务与流程,接地气
  2. 可以统括大家的日常(至少是测试相关)工作,并切实有效提升工作效率,而不是可有可无的鸡肋,甚至无疾而终的累赘
  3. 由我们自主开发,既可以随时随地改进平台符合需求,又可以锻炼队伍,提升能力

从功能上讲,可以大致分为:

  1. 帮助大家更好的管理和执行测试
  2. 展现与提炼测试过程与结果

前者对于测试人员更实用,同时可以产出更多的测试内容供后者展现;后者领导会更关注(领导重视确实重要==!),同时也有助于测试人员改进测试

孰轻孰重,在资源与经验不足的情况下如何协调?

以上是感悟,以下是吐槽

  1. 瓜不熟不落,与其强扭,不如耐心培育若干好苗子,积攒经验,同时做好调研与技术预研,期待后期发力
  2. 一群人每周开一次会研讨,不如一个人全职跟进

以上是吐槽,以下是结论

服从组织安排,保留个人意见

Ruby学习系列 - 基础知识 - Array

序言

本着赶鸭子上架及边学边做的精神,总也算是写了好一些Ruby代码;但回过头来发现自己的进步不大,写代码还是很生涩,不上道,多次在基础知识上摔跟头

新的一年开始了,希望自己能够扎实掌握Ruby这项技能,从基础开始,梳理一些知识点

第一部分讲Array,取材于Ruby core API,加以归纳整理,便于记忆

创建

If multiple copies are what you want, you should use the block version which uses the result of that block each time an element of the array needs to be initialized:

1
2
3
a = Array.new(2) { Hash.new }
a[0]['cat'] = 'feline'
a # => [{"cat"=>"feline"}, {}]

赋值

1
2
3
4
5
6
7
8
9
a = Array.new
a[4] = "4";                 #=> [nil, nil, nil, nil, "4"]
a[0, 3] = [ 'a', 'b', 'c' ] #=> ["a", "b", "c", nil, "4"]
a[1..2] = [ 1, 2 ]          #=> ["a", 1, 2, nil, "4"]
a[0, 2] = "?"               #=> ["?", 2, nil, "4"]
a[0..2] = "A"               #=> ["A", "4"]
a[-1]   = "Z"               #=> ["A", "Z"]
a[1..-1] = nil              #=> ["A", nil]
a[1..-1] = []               #=> ["A"]

取值

1
2
3
4
a = [ "a", "b", "c", "d", "e" ]
a[1, 2]                #=> [ "b", "c" ]
a[1..3]                #=> [ "b", "c", "d" ]
a[-3, 3]               #=> [ "c", "d", "e" ]
1
2
3
a = [ "q", "r", "s", "t" ]
a.first     #=> "q"
a.first(2)  #=> ["q", "r"]
1
2
3
a = [ "w", "x", "y", "z" ]
a.last     #=> "z"
a.last(2)  #=> ["y", "z"]

运算

1
2
3
4
[ 1, 2, 3 ] + [ 4, 5 ]    #=> [ 1, 2, 3, 4, 5 ]
[ 1, 1, 2, 2, 3, 3, 4, 5 ] - [ 1, 2, 4 ]  #=>  [ 3, 3, 5 ]
[ 1, 2, 3 ] * 3    #=> [ 1, 2, 3, 1, 2, 3, 1, 2, 3 ]
[ 1, 1, 3, 5 ] & [ 1, 2, 3 ]   #=> [ 1, 3 ]

增减

1
[ 1, 2 ] << "c" << "d" << [ 3, 4 ] #=>  [ 1, 2, "c", "d", [ 3, 4 ] ]
1
2
a = [ "a", "b", "b", "b", "c" ]
a.delete("b")                   #=> "b"
1
2
3
a = %w( ant bat cat dog )
a.delete_at(2)    #=> "cat"
a                 #=> ["ant", "bat", "dog"]
1
2
a = [ "a", "b", "c" ]
a.delete_if {|x| x >= "b" }   #=> ["a"]
1
2
reject {|item| block }  new_ary
reject  an_enumerator

Returns a new array containing the items in self for which the block is not true. See also Array#delete_if

If no block is given, an enumerator is returned instead.

1
2
reject! {|item| block }  ary or nil click to toggle source
reject!  an_enumerator

Equivalent to Array#delete_if, deleting elements from self for which the block evaluates to true, but returns nil if no changes were made. The array is changed instantly every time the block is called and not after the iteration is over. See also Enumerable#reject and Array#delete_if.

1
2
3
a = %w{ a b c d }
a.insert(2, 99)         #=> ["a", "b", 99, "c", "d"]
a.insert(-2, 1, 2, 3)   #=> ["a", "b", 99, "c", 1, 2, 3, "d"]
1
2
3
4
5
6
7
a = [ "a", "b", "c" ]
a.slice!(1)     #=> "b"
a               #=> ["a", "c"]
a.slice!(-1)    #=> "c"
a               #=> ["a"]
a.slice!(100)   #=> nil
a               #=> ["a"]
1
2
3
4
a = [ "a", "b", "c", "d" ]
a.pop     #=> "d"
a.pop(2)  #=> ["b", "c"]
a         #=> ["a"]
1
2
a = [ "a", "b", "c" ]
a.push("d", "e", "f") #=> ["a", "b", "c", "d", "e", "f"]
1
2
3
args = [ "-m", "-q", "filename" ]
args.shift     #=> "-m"
args           #=> ["-q", "filename"]
1
2
3
args = [ "-m", "-q", "filename" ]
args.shift(2)  #=> ["-m", "-q"]
args           #=> ["filename"]

变换

1
2
3
a = [ "a", "b", "c", "d" ]
a.collect {|x| x + "!" }   #=> ["a!", "b!", "c!", "d!"]
a                          #=> ["a", "b", "c", "d"]
1
2
3
a = [ "a", "b", "c", "d" ]
a.collect! {|x| x + "!" }
a             #=>  [ "a!", "b!", "c!", "d!" ]

collect等效于map

1
[ "a", "b" ].concat( ["c", "d"] ) #=> [ "a", "b", "c", "d" ]
1
2
[ "a", "b", "c" ].join        #=> "abc"
[ "a", "b", "c" ].join("-")   #=> "a-b-c"
1
[ "a", "b", "c" ].reverse   #=> ["c", "b", "a"]
1
2
3
a = [ "a", "b", "c" ]
a.reverse!       #=> ["c", "b", "a"]
a                #=> ["c", "b", "a"]
1
2
3
a = [ "d", "a", "e", "c", "b" ]
a.sort                    #=> ["a", "b", "c", "d", "e"]
a.sort {|x,y| y <=> x }   #=> ["e", "d", "c", "b", "a"]
1
2
a = [ "a", "a", "b", "b", "c" ]
a.uniq   # => ["a", "b", "c"]
1
2
b = [["student","sam"], ["student","george"], ["teacher","matz"]]
b.uniq { |s| s.first } # => [["student", "sam"], ["teacher", "matz"]]

统计与查询

1
2
3
4
ary = [1, 2, 4, 2]
ary.count             #=> 4
ary.count(2)          #=> 2
ary.count{|x|x%2==0}  #=> 3
1
2
3
a = [ "a", "b", "c" ]
a.include?("b")   #=> true
a.include?("z")   #=> false
1
[ 1, 2, 3, 4, 5 ].length   #=> 5
1
2
a = %w{ a b c d e f }
a.select {|v| v =~ /[aeiou]/}   #=> ["a", "e"]
1
[].empty?   #=> true

其它

1
2
a = [ "a", "b", "c" ]
a.each {|x| puts x }
1
2
a = [ "a", "b", "c" ]
a.each_index {|x| puts x } # passes the index of the element instead of the element itself

小结

Array包含很多API,以上只是我个人当前认为比较常用的一部分,后续会再调整

下面介绍HashString

新博启用

由于原博客在功能和形式上都不能很好符合我的需求,再加上我爱折腾的怪癖,终于决定启用此博客

本博客立志于

认识自己 认识世界

但在达成这一宏愿之前,将主要发布与我当前职业(一名有态度,爱折腾的QA)相关的文章;同时,也会陆续从原博客整理、搬运一批文章过来

本博客依托于Github,使用octopress搭建博客,期间参考了

  1. 如何知道了octopress这玩意 传送门
  2. octopress官网指南 传送门
  3. octopress简单使用,内容类似官网指南,但更具体一些 传送门
  4. 如何使octopress支持中文分类标签 传送门