天行健，君子以自强不息 » 软件测试

缺陷工作流程和缺陷报告

ricky.zhu — Sun, 25 Jul 2010 15:04:54 +0000

最近在读《How We Test Software at Microsoft》
其中的缺陷和测试用例管理，发现很多思路和做法跟目前我们在进行的也颇为相似，总结如下：

缺陷管理和用例管理是一个软件测试项目的必备，无论是数千人的国际化大企业，还是三五人的小软件作坊。这都是测试队伍的两大工作成果。其中，测试用例描述测试
过程的意图，缺陷则描述这些测试用例的结果。，今天谈谈缺陷工作流程。

缺陷工作流程为:

文字描述如下:
产品代码-》运行测试用例-》创建缺陷报告-》三方会审讨论缺陷
如果缺陷没有批准-》把缺陷当作不修正来解决-》关闭缺陷
如果缺陷批准了要调查-》研究是代码错误还是设计错误
如果是代码错误，提议修正代码错误-，在提交三方会审-》如果修正批准了-》修改代码-》解决缺陷-》重现缺陷-》通过了则关闭缺陷；不通过，则重新激活-》重新调查是代码错误还是设计错误
如果是设计错误，修正错误直到批准-》再进行三方会审。其他后续流程和以前类似。

在这里需要注意的是，有些缺陷需要综合考虑优先级别，产品发布周期等因素，标注为不予修复。也就是说虽然承认该缺陷，但不会修正，或者决定推迟修正，即该缺陷会在未来的版本修正。这些不予修正的缺陷应该在release notes中予以注明。

这里所说的三方会审，一般意义上指的是开发测试和项目管理。

缺陷报告中应该经常避免的几个错误：
1.电子邮件讨论
电子邮件和缺陷系统是大多数的工程师常用的工具，所以很多时候两者被混用就不足为怪了。然后除了开发工程师和测试工程师之外，缺陷报告还有其他的广泛用途，所以和缺陷不直接相关的信息不应该被写入报告。
2.缺陷渐变
缺陷渐变是说在同一个缺陷的报告中，缺陷从一个问题演变成另外一个不相关的问题。这种现象有时候发生很快，有时候过几天或者几个月。不管怎么样，都要极力避免缺陷渐变。对于已经变形的缺陷，通常很难分析其中根本原因，产品支持工程师在搜索相关问题时候还会发生混淆。如果一个缺陷报告开始演变，要及时停止，并就新问题重新报告一个新的缺陷。
3.对个缺陷
如果测试人员很忙碌，他们可能会相关的缺陷记录放在一个缺陷报告中。尽管我们尽力避免这类问题，在一个缺陷报告中报告几个问题从来就不是好主意。这会带来一系列的问题，比如：
(1)缺陷的优先级别不能单独设置
(2)缺陷的决定不能单独设置，比如立即修复还是推迟到下一版本
(3)虽然缺陷在类似领域，但是可能需要分配给不同的开发工程师
(4)在分析产品缺陷的根本原因时候，同一缺陷报告中的每个缺陷可能有不同的错误根源。

关于缺陷报告的时候
这似乎是管理层最喜欢干的事情，这些报告发掘和代表了各种各样的数据。比如下面的一些度量：
(1)修复的缺陷/所有解决了的缺陷：可以衡量缺陷修正和其他决断的比例
(2)缺陷发现率
(3)缺陷修正率：当缺陷会审标准提高时候，修正的百分比下降
(4)每个组件的缺陷数：根据功能排序可以影响哪些领域需要更多的测试
(5)如何发现缺陷：了解缺陷如何发现可以帮助根源分析和实现缺陷防止技术
(6)每个测试活动发现的缺陷：分析测试类别包括结构化测试，发布前测试，测试用例开发，自动化测试等
(7)平均解决缺陷的时间：跟踪开发团队对输入的缺陷的响应速度
(8)平均关闭缺陷的时间：跟踪缺陷的平均反应时间

缺陷数据唯一不能使用的时候：绩效衡量
缺陷数据具有太多的可变量，比如：
(1)所测试功能的复杂性
(2)开发人员的编程能力
(3)规格完整性
(4)缺陷预防和缺陷发现
(5)报告的及时性

下节谈谈测试用例管理。

StAREAST and STARWest

ricky.zhu — Tue, 20 Jul 2010 04:53:34 +0000

今天介绍一下这两个非常有名的测试行业的权威组织，STAREAST 和 STARWEST。
顾名思义，这是分别在美国东部和西部举行的测试行业的一个高端盛会。这两个会议自从2000年开始举行，到今年已经是第十个念头了，每次的会议大概持续6天。前面五天是一些测试的主题演讲和技术展示，介绍的是测试行业的最新的技术，方法，工具等。而演讲嘉宾也都是行业的大师级别的人物。最后一天是一个软件测试和质量领导人论坛。

今年的STAREAST，也就是东部的盛会已经于4月25到30日在东部城市奥兰多闭幕，详细情况参考这里

2010年的STARWEST也筹备结束，将于2010年9月26－10月1日在美丽的西海岸城市加州的圣地亚哥举行。

下面是STAREAST今年6天中的第二天的演讲内容，其中包论的内容十分广泛，包括风险驱动的测试，测试设计技术，移动终端的测试自动化技术等等，当然也包括如今比较热门的敏捷测试等话题。今年的全部日程参考这里

《日程格式太乱，就不贴了，大家去原链接查看》

另外，这个会议的演讲者也是可以自己申请的（申请2011的演讲），忠心希望能有一天国内的测试同行有机会站在这样的国际会场上。分享我们自己的对于测试的理解和经验。

其实我第一次听过这个会议是2004年，我当时的Test Manager Rosa参与了STARWEST并带回了大量精彩现场的演讲的PPT，并指导我们当时的公司和团队顺利的从无到有成功的开展了自动化测试，最终在企业范围内搭建了一个自动化测试平台，并组建了一支强竞争力的自动化测试团队。早在2004，2005年的时候我们就完成了这一个在现在看来都十分了不起的成就，即便不是第一个，也是当时为数不多的比较成功的自动化测试的案例。

几句题化话：
我们当时的成功很大程度上归功于Rosa的丰富的测试经验和强有力的领导以及执行力。后来他虽然也离开了我们回到了美国，但是一直都有保持联系。

用户界面测试的颠覆性技术-Sikuli

ricky.zhu — Wed, 27 Jan 2010 14:59:35 +0000

Sikuli绝对是一种颠覆性的技术，至少对于GUI的测试技术来说，是质的突破，比如它彻底解决了在这之前GUI自动化测试工具上的关键点-对象识别。

技术来自于从麻省理工学院计算机和艺术智能实验室的一个用户界面设计小组的研究项目，Sikuli脚本和Sikuli开发平台基于MIT License发布，是开源的。

什么是Sikuli
========
Sikuli是一种利用图片（快照）去搜索和自动化GUI的视觉技术，Sikuli的第一个release包含Sikuli脚本，也就是为Jython编写的一种视觉脚本API，同时包含了Sikuli IDE，一个可以非常容易的用快照书写视觉脚本的集成开发环境。Sikuli脚本可以自动化你在屏幕上看到的一切，而这不需要内部API的支持。你可以编程控制一个页面，一个运行在Windows/Linux/Mac OS X上的桌面应用程序，甚至于一个运行在模拟终端的iphone的应用程序。

Sikuli的必杀技
========
自动化所有你看到的一切
利用快照进行自动化
工作在Java平台（意味着可移植）

Sikuli安装和使用
===========
下载安装了一下，在Windows上需要JDK1.6以上环境，这里有一个简单的视频介绍（看不到youtube的同学翻墙吧）。

不会翻墙的地同学请从如下视频观看：

继续阅读论文
=========
GUI Testing Using Computer Vision

Sikuli: Using GUI Screenshots for Search and Automation

MIT news介绍图像驱动计算

一个例子快照
=========

拭目以待！

测试如何同开发搞好关系

ricky.zhu — Wed, 09 Dec 2009 04:44:01 +0000

测试跟开发是一对死对头。
你还在用这样的观点看待测试人员和开发的关系吗？
你已经out了。

测试人员跟开发的关系一直是一个矛盾的话题，如何处理和测试跟开发的关系，保持步调一致，把过程中的矛盾和对立统一到共同为提高产品质量这个主题和最终目标上来，是一个体力活，更是一门艺术。

这篇文章总结的不错，因为比较浅显易懂，就不一一翻译了，最终作者总结了四点：

Tip #1: Don’t editorialize the bugs you find.
要理解开发人员，他们有时候也面临很大的压力，有时候犯一些低级的错误是难免的，要学会宽容。

Tip #2: Stay in sync with the development cadence
要跟开发保持同步，有时候你提交的bug得不到反馈并不是他们没看到，也不一定是问题不重要，要保持沟通，步调一致。

Tip#3: Isolate bugs effectively
提交bug之前要对bug进行初步的分析和简单的有效的定位，而不是发现问题立即就提交，最好能够问自己几个问题：

1）是否已经发现了能够重现问题的最简单的路径（Ricky注：很多时候发现一些测试人员提交bug的时候描述步骤是做了a, b, c, d, e … f, g, h 然后问题出现，其实经过追踪，发现问题出在f-g这一步，前面的一些都是无关的操作，要学会简单的定位问题，这不仅仅节省了开发人员的时间，而且节省了自己的时间）
2）是否弄错的程序的版本（Ricky注：很多时候，我们发现问题，往往是因为拿错了程序的版本或者问题在被测的版本中是已知的，这就要求在测试之前特别是提交bug之前，首先检查下版本信息和known issue）
3）是否已经排除问题是因为自己的环境配置问题导致（Ricky注：有时候一些问题往往是环境配置所致，这个时候检查一下，是否是环境问题，在别的环境或者不同配置的情况下是否可以重现）

Tip #4: Sleep on bug reports
提交bug report之前要预留一点时间，给自己一点缓冲，也跟开发人员一点余地。比如作者自己的一个办法就是写好bug之前，等一晚上再提交，第二天提交之前用自己的描述的步骤重现一次，看看是否还可以重现问题。

参考原文

测试工程师是否需要懂开发

ricky.zhu — Mon, 20 Jul 2009 14:24:35 +0000

这是测试界的一个永恒的话题：测试工程师是否需要懂开发（或者叫会编码）

文中论述的十分充分，最后的结论是 it depends，我在很大程度上十分同意文中的观点。我的观点是“测试工程师不一定要懂开发，但是懂开发可能对你的测试职业发展有很大的帮助”

原文地址

Am I a Tester or a Programmer? Who am I?

Abhijit Navindgikar: “I am having one question regarding software testing. Currently I am working as a software tester. I am having 3 years of experience in manual testing and having the basic knowledge of C/C++. Is it necessary for me to learn new technologies like C# .NET for future prospects in testing? Is it necessary for the tester to have the programming skills also? (Till know I didn’t feel that tester need to know the programming but let me know your views). Also will it be possible for a black box tester to shift his career to white box testing? If yes what steps need to follow to start the same?”

Lakshmi: “Recently I was browsing some of the testing sites and came to know that “No knowledge on programming language is a hindrance to a tester’s career”. Is that correct? Really, programming language knowledge is that much necessary for a tester? I am not able to digest this. Please help me.”

John: “My test manager feels that all testers must have decent programming skills. He is so much obsessed with his belief that I fear he may go ahead and fire testers who are not so good in programming (even though they are quite good at testing). Is there a way to change his mindset without hurting his ego?”

These are excerpts of few emails from my inbox. These are kind of questions that always have made me to think. Every time I think on these questions, some more questions start popping up in my mind. Questions like:

1. Knowledge of programming and effectiveness of a tester – is there a connection?

2. Can a good programmer make a good tester?

3. Can a bad programmer make a good tester?

4. Can a non-programmer make a good tester?

5. Can I think of contexts when knowledge of programming can enhance my testing?

6. Can I think of contexts when knowledge of programming can hamper my testing?

7. Can I think of contexts when ignorance of programming can enhance my testing?

8. Can I think of contexts when ignorance of programming can hamper my testing?

9. The list of questions continues…

I have seen quite a lot of such “Do testers need programming knowledge” kind of debates, especially since Microsoft started distinguishing its testers as Software Test Engineers (STE) and Software Design Engineers in Test (SDET)! And this debate gathered momentum as Microsoft started shifting weightage from STEs to SDETs while hiring (and firing) test engineers! However, I am not going to extend the STE Vs. SDET debate in this particular post of mine. Rather I will try to focus on the need of programming knowledge for a tester.

To me the single sentence answer for the question “Do I need programming skills to excel as a tester” can be – “It depends”. It depends on your particular context, the type and complexity of the AUT [Application Under Test] and more importantly your testing mission. Blindly hiring testers who can code may prove to be a bad idea, especially if you are neglecting your testing mission while taking such a biased decision!

Having said that, there can be contexts where a tester who can code, can be an asset for the test project. Think of scenarios where testers need to automate GUI tests. Even if the tester might be using some so-called record-and-playback kind of tool (WinRunner, QTP, IBM Rational Robot blah blah…), knowledge of programming, can be an added advantage. That can allow a tester to tweak his tests at script level to make them more powerful and flexible! e.g. The tester need not re-record his tests each time a object name for a recorded test object is changed (may be due to recent code refactoring). He can simply go and change that particular object name from the script. As Danny Faught talks in this interview, “Test automation requires programming skills. Plain and simple, no way around it. No tool can get around that.”

In cases where the organization (or the client) can not afford acquiring license for costly automation tools, the programming skill (in most cases knowledge in some scripting languages like Perl, Python, Ruby, JavaScript and markup languages like XML, XSLT) can help the tester in setting up a home-grown test driver framework to cut down the license cost of Commercial tools and at the same time can result in a customized tool that fits better for your testing requirement. Forget about test automation, testers with programming skills may detect defects earlier in development cycle and may also be able to pin point the cause for the defect (provided that the tester is aware of the underlying code and the system architecture). This may also help the tester in finding other areas in code where there can be similar errors. A tester who has a development background can also participate in code reviews, can debug problems, perform unit testing and identify patterns in the code that are error prone. If you are a tester, knowledge in programming can sometimes earn you greater credibility among the programmers.

But does this mean a tester without coding skills is useless? Of course not! To say Manual Testing (Sapient Testing, the James Bach way) is losing its value, in my opinion, is too early to jump into any conclusion. With user’s expectations increasingly higher, it would be foolish to lower its value. How many testers do unit testing in this agile era of software development (where the programmer has to write unit tests for his own code snippet)? A good tester is a good tester for his ability to test, not for his ability to code! After all, a tester gets paid to test, not to code. Although coding background can help in certain contexts to test better, that should not be over-generalized! Test automation can never replace manual testing. I think, the same can be safely said about programming skills of a tester. A tester with coding skills can not replace a tester without coding skills. If asked to test an application, both of them will find different sets of defects. Think of user experience/interface related defects for example. Or for that matter, think of scenarios where you don’t have enough time to test. Would you sit down to do code review and perform a cause and effect analysis using your programming skills or would you rather exploratory test it right away?

If I were a test manager, I would rather hire testers both with and without coding skills. Testing is all about flexibility! Each and every member of the testing team can’t be expected to have equal skill sets and equal areas of expertise. Testing as a craft is evolving into different specializations and it must be understood that each kind has its own importance. So it always helps to have a testing team comprising of a variety of skill sets. Testers with different specializations (with or without coding knowledge) are not mutually exclusive rather they should compliment each other. What do you think?

Happy Testing…

开源数据库性能测试工具HammerOra介绍

ricky.zhu — Sun, 19 Jul 2009 15:07:52 +0000

前段时间发现了这个工具，并粗略研究了一下，工具是基于TCL（Tool Command Language）语言的（我之前用Tcl工作过好几年，之前自动化框架就是基于Tcl来开发的，Tcl是非常优秀的自动化脚本语言）

首先HammerOra 是一款负载测试工具

其次HammerOra目前支持Oracle, MySQL和HTTP应用（web应用）

然后HammerOra是开源的，框架有点类似于商业工具LoadRunner

因为HammerOra是基于Tcl语言的，所以天生就是可移植的，可以运行于Windows平台和Linux平台。

HammerOra内嵌了两套标准测试脚本 tpc-c and tpc-h，当然你也可以自己开发和扩充测试脚本，开发语言是Tcl

HammerOra包含三个部分（这点有点类似于LoadRunner）创建测试脚本（打开build-in的tpc-c or tpc-h）然后可以进行调试；配置并创建虚拟用户，并设置虚拟用户的策略，比如持续时间，用户迭代，rumpup原则等，然后控制场景运行；最后是监控事物计数器。对应于LoadRunner分别是VUGen, Controller and Analysis

HammerOra的工作原理就是捕捉Oracle的trace文件，并生成相应的SQL脚本进行回放，所以对用户的场景模拟程度是非常高的。HammerOra跟Oracle的接口是也是利用一个Tcl的package OraTcl来完成的。（之前我们在开发测试平台时，后台驱动Oracle数据库操作也是通过这个package来完成的；记得我面试oracle第一个职位的时候，美国的同事还问到关于这个Package的几个问题）

HammerOra的安装非常简单，一种是源码安装，还是就是安装包安装，就不多做介绍了，可以参考官方文档。

如果你要对数据库进行性能测试，预算有限的话，可以考虑这款优秀的开源工具。

脚本界面：

场景界面：

结果界面：

庆祝51Testing软件测试网成立五周年

ricky.zhu — Thu, 30 Apr 2009 09:06:51 +0000

真快啊，不知不觉，都已经五年了。
首先祝福51testing生日快乐。

虽不是51最早的一批注册会员，但是从事测试这个行业也超过5年了，而且也算国内比较早专职作自动化测试的团队和成员了，关于这段光荣史，有空还要好好续一下。

这5年可以说是国内测试行业迅速发展的5年，依靠这5年的努力，51testing早已经是国内测试行业的一块金子招牌了。

祝贺老李和老周，也期待51接下去有更大的发展，成为真正的中国测试行业的黄埔军校。

不知道看我blog的朋友有没有不知道51testing的，如果不知道的话，网址在下面。

51Testing软件测试网：http://www.51testing.com

看看51的发展轨迹：

2004年5月，51Testing网站和论坛相继成立
2004年12月，51Testing会员数达一万
2006年12月，51Testing博客面向会员开放
2007年1月，51Testing会员超过十万
2007年3月，51Testing改版，采用全新的内容管理系统，全新的版面，并沿用至今
2007年5月，51Testing三周年庆
2007年7月，电子杂志《无忧测试》重新发布，并更名为《51测试天地》，每季度一刊
2007年9月，51Testing发起《2007年首届中国软件测试从业人员调查活动》，并于2008年4月发布调查报告
2008年6月，由51Testing组编的第一本软件测试系列丛书开始上市销售
2008年6月，51Testing启动《2008年首届企业软件测试现状调查活动》，并于2008年12月发布调查报告
2008年9月，51Testing会员超过二十万
2009年4月，51Testing会员突破二十五万，全面开展五周庆典活动……

Automate your Web Application with Oracle ATS

ricky.zhu — Wed, 29 Apr 2009 13:05:23 +0000

Oracle Application Test Suite （Oracle ATS）是基于Oracle收购的e-Test Suite技术而构建的企业自动化测试解决方案，也是Oracle Enterprise Manager的一部分，

随着更多的工具被集成到Oracle EM中来，这个Oralce的策略性产品也在变的越来越强大，最新的EM版本已经是10.2.0.5了，免费下载地址如下：下载地址

今天重点介绍一下Oracle EM中的ATS，以后Ricky会陆续关注EM中的其他组件。

Web application quality and performance issues can have major impact on your bottom line – impacting revenue, customer loyalty and satisfaction and your company’s reputation. However, even today, industry studies suggest that 75% of applications are still deployed without adequate testing. The majority of functional testing that is performed is still done manually and load testing prior to deployment to assess and tune application performance is not a common practice.

Join us for this live 1-hour presentation where we will introduce Oracle Application Testing Suite, a new offering from Oracle Enterprise Manager, and show how it can help you automate your functional and regression testing, automate your load and performance testing and manage your overall test process.

During this presentation you will see a live demo of the following Application Testing Suite solutions:

* Oracle Functional Testing for Web Applications
* Oracle Load Testing for Web Applications
* Oracle Test Manager for Web Applications

视频地址

jackal the divx
其他系列的关于EM的视频讲座，参考链接地址

Three Key Tools for Test Automation

ricky.zhu — Tue, 28 Apr 2009 13:16:04 +0000

很久没有静下心来写写测试方面的总结了，打算忙完了这个重要的Release，就沉下心去，好好总结几篇，这两年在Oracle从事质量工作的一点体会，也不辜负长期以来一直关注和支持我的朋友。

前几天看到一篇非常不错的关于自动化测试架构的文章，分享一下。原文链接

文章讲的是自动化测试的三个关键：开发语言，平台和工具。这是自动化测试非常核心的三个关键点，但往往也不是那么容易把握或者考虑全面的。参考原文先：

Three Key Tools for Automated Testing: Language, Driver, Harness

When I started working on Watir, I was pushing a vision for automated testing. This vision still motivates my work with Watir. A couple of years ago, Brian Marick told me open-source developers should share their vision and let the community know why they built the tool. Here’s the vision.

There are three essential elements of an automated testing system: language, driver and harness. Your tests need to be written in a language and you need a language to extend your testing system. I’ve long believed in scripting languages, such as Perl, Python and Ruby. I find that testers are more productive with them and find them easier to understand and use. I have reasons why I prefer Ruby, but there are other good automated testing systems written using other scripting languages. In fact over the years, I have built testing frameworks in Perl, Python and VB, usually building on languages that were already in use at the client. My emphasis on full-featured programming languages was a contrast to the proprietary languages

that had been commonly used in commercial testing tool suites. I had no patience for them.

There are lots of languages to choose from. Finding a suitable driver, however, was often more difficult. A driver is what you need to drive your application. Watir is an example of a browser driver, suitable for web applications. Often the driver determines the language you use. Years ago, I used Expect as a driver for a command line application. Expect used TCL as its language, so the suite was written in TCL. I developed Watir because I wanted a browser driver in Ruby. Watir was our solution for Web Application Testing in Ruby.

The third thing you needed for a testing system was a harness. When we started, we all used Test::Unit, a Ruby test harness designed for unit testing. We found that it could be adapted for functional testing. More recently, Watir users have been using Rspec or Cucumber as their test harness. A test harness is responsible for executing tests and collecting and reporting results. Some people like to build their own test harnesses instead of using one of these.

I developed this vision while working with commercial testing tool suites like SilkTest and WinRunner. These packages are often referred to as tools, but I found that they actually comprised a collection of integrated tools. They had predefined usage expectations that often didn’t match actual tester needs. Data-driven testing, for example, required us to break down the suite and then reassemble it in a more suitable configuration. I wanted testers to be able to identify the individual tools that made up a testing system.

Many new Watir users have trouble identifying where Watir (the driver) ends and Ruby (the language) begins. But learning this is key to becoming a proficient user. I’m told that some Java teachers don’t like their students to use an IDE (such as Eclipse or Netbeans). Instead they want their students to learn to use the required tools separately — the editor, the compiler. This way they learn the function of each tool. In the same way, I’ve also wanted testers to understand the functions of the different tools and components used in a testing system.

We often get questions from new Watir users whose answers are obvious once you understand this. Can Watir read CSV files? Can it do date math? Can it read from a database? The answer to all of these questions is that Watir can’t do it, but Ruby can. No browser driver could do these things (it would be like asking whether your compiler supports search and replace), but any full-featured programming language can. It’s just a matter of finding the library to do it. These questions are raised in the first place because testers are used to using commercial tool suites that were closed systems. So you only got the ability to do these kinds of things if the vendor added it to the package. Watir is part of an open system, so all the libraries are there already and more are being written all the time, often by people who are not part of the Watir community, per se, but rather part of the larger Ruby community.

Want to learn more? I am teaching classes jackal the movie download on Watir, Ruby and the new WatirCraft framework that supports both Rspec and Cucumber.

Oracle RAC Team Hiring-Urgent

ricky.zhu — Sat, 07 Mar 2009 12:41:07 +0000

This is a bit Urgent. Oracle RAC Development team is Hiring. Prefer base is Shenzhen and Beijing

Special Requirements:

* must be new graduate this year with master degree in Computer or Science related field.

* must graduate at top 10 university.

Below please find the job description, this is the golden opportunity to learn the Oracle core technologies in the Sever Technologies division. If you think the work is a good fit with your interests. Please send your CV based on the contact information of the job description.
The following URLs can provide more information about RAC

http://www.oracle.com/technology/products/database/clustering/index.html

http://www.oracle.com/database/rac_home.html

Oracle RAC is the crown jewel in the company. We own the most fast growing core product with advanced technologies.

Detailed as below:

POSITION DESCRIPTION

Job title: Associate Member of Technical Staff, Server Technologies

Department: Real Application Cluster (RAC) Development.

Category: Oracle Clusterware , RAC Clustering and RDBMS testing

Contact: Winston.Huang@oracle.com or Rung-Huang.Tsai@oracle.com

Brief Description:

Responsible for RAC-DB stability, performance testing and Clusterware destructive testing on varies platforms; responsible for understanding RAC functionality, Oracle rdbms and asm new features and Oracle clusterware on varies releases and responsible for implementing, maintaining, and enhancing test infrastructure/tools and verifying testing results.

This is the golden opportunity to learn Oracle within Oracle, the challenging position provides training to lay the foundation of RAC and database stability, High Availability. Engineer will expose to latest Oracle technologies on varies platforms. Those experiences are extremely valuable toward the building solid foundations of RAC and High availability systems for future system architecture integration and consulting work.

Detailed Description:

· Logs and tracks product defects as encountered.

· Specific Projects include: RAC stability testing and Oracle Clusterware testing:

o Understand the vulnerabilities for each release.

o Ensure quality of post-release bundle deliverables by understanding new feature/enhancement and verifying various fixes.

o Enhance the test tools/infrastructure, aim to an automated testing framework with flexibility and simplicity.

o Understand RDBMS functions, especially in RAC environment, for detecting failure in functionality and usability.

· Various Workload understanding, placement, maintenance and enhancement.

In addition to tasks described above, the incumbent will also participate in additional tasks with other senior team members, e.g.:

· Product testing (beta and pre-release stress/destructive tests)

· Product training and user documentation review

Technical Background:

· Good understanding of database concept, architecture and terminology.

· Proficiency in Perl and other scripting languages; and plsql

· Good grasp in programming language and operating system level knowledge.

· Knowledge in software engineering and system software testing is a plus.

· Knowledge in Oracle database or Plsql is preferred.

Personal Profile / Skills:

· Quick and willing to learn, self-motivator, attention to details and team player

· Good verbal and written communication skills in English

· Ability to multitask and deliver under pressure

· Good academic records for entry-level position, new graduate welcome

天行健，君子以自强不息 » 软件测试

缺陷工作流程和缺陷报告

Related Posts

StAREAST and STARWest

Related Posts

用户界面测试的颠覆性技术-Sikuli

Related Posts

测试如何同开发搞好关系

Related Posts

测试工程师是否需要懂开发

Related Posts

开源数据库性能测试工具HammerOra介绍

Related Posts

庆祝51Testing软件测试网成立五周年

Related Posts

Automate your Web Application with Oracle ATS

Related Posts

Three Key Tools for Test Automation

Three Key Tools for Automated Testing: Language, Driver, Harness

Related Posts

Oracle RAC Team Hiring-Urgent

This is a bit Urgent. Oracle RAC Development team is Hiring. Prefer base is Shenzhen and Beijing

Related Posts