天行健，君子以自强不息

Refer from Jackei’s blog post in 2005
Havn’t write posts about testing for a long time and now have moved to Linux OS so can’t input Chinese.

原文出处：http://blog.51testing.com/index.php?op=ViewArticle&articleId=1463&blogId=130

做IT的苦，做IT职业中的测试更苦，你先别看这个职业有没有前途，先看看进入这个职业所要忍受的痛苦。没有正点吃饭的，没有正点睡觉的，N个发布基线的压力，N种不信任你的眼神…。

只知道进入这一行的有很多是新虫，新虫子总是很澎湃的投入工作，不过我更愿意看到这些新虫子投入到大公司工作，这是个反话。在大公司里做测试根本就不要想有分工明确、人力和辅助资源丰富、培训机会多多、工资优厚这
些条件，我告诉你在大的公司里有一句箴言“人干什么都要靠自己，千万别指望别人”。

不过我愿意吃苦，现在我的心理跟当初刚进大公司有了不同，我发现我还是处在技术第一线，我发现了我以前做测试就象是小孩在玩游戏，说真的没用过Unix真不知道windows的烂，呵呵。现在我测试的东西是标准的
MVC，前台windows的，中间层第一层CORBA，使用Oracle的数据库，我每天都在Unix上测试几组的移动业务，前台是个摆设只有我想验证前台的操作功能是否正确的时候才回去点击几下，在这里我想跟
所有的测试朋友说：

$不要相信前台抛出的Message对话框，除非某些信息你真的想得都得不到。

阅读全文 »

Share This

中高端测试工程师行情看涨，我们能做的是什么呢，就是努力跻身中高端，赫赫，下面转载一篇新闻：

随着中国软件市场的发展，其潜力和机会已经远超“软件王国”印度，虽然有越来越多的国外资金投进来，但由于人才严重不足等问题，我国软件业发展正遭遇“瓶颈”。

在近日举行的2007上海软件外包国际峰会上，与会专家纷纷呼吁，培育我国软件外包中高级专业人才是重中之重。

市场国际化，人才需求大

据介绍，目前上海软件产业从业人员已达15万人，今年软件产业经营收入有望超过800亿元，同时，已经登记的软件出口企业有200多家，出口额达到9.9亿美元，同比增长49.7%，但其增长势头与大量国内外软件巨头齐聚上海的势头相比仍相形见绌。

SAP、微软等各大全球知名企业早已进入中国，再加上中国现有的大量中小规模的软件开发公司，这就构成了上海乃至全国的软件行业规模庞大的雇主群体。据国家信息产业部的行业预测数据，2010年，中国软件产业销售收入预计将达13000亿元，未来几年的年增长率将不低于30%。在这一态势下，对人才的需求将持续放量。
阅读全文 »

Share This

假期马上结束了，这阵子一直比较忙，所以测试知识问答系列中断了一段时间，现在补上。
另外，很多朋友问我这些问题从哪里收集来的？其实细心的朋友应该能从我的博客圈子里面找到，这就是从著名的Rob（巨牛的一个人的网站）的个人博客转载来的，Rob有着超乎常人的丰富的项目经历和知识背景，而且他的博客上有超过上百个页面的知识问答，我这里仅仅摘抄一部分个人认为比较经典的部分，有兴趣的朋友可以去这个地址详细访问：
http://www.softwaretestengineer.com/free2/index.html
http://www.softwaretestengineer.com/free/index.html

Q: Which of these tools should I learn?

A: Learn ALL you can! Learn all the tools that you are able to master! Ideally, this will include some of the most popular software tools, i.e. LabView, LoadRunner, Rational Tools, WinRunner, etc. You want to pay special attention to LoadRunner and the Rational Toolset.
阅读全文 »

Share This

Q: What is the purpose of test strategy?

A: Reason number 1: The number one reason of writing a test strategy document is to “have” a signed, sealed, and delivered, FDA (or FAA) approved document, where the document includes a written testing methodology, test plan, and test cases.

Reason number 2: Having a test strategy does satisfy one important step in the software testing process.

Reason number 3: The test strategy document tells us how the software product will be tested.

Reason number 4: The creation of a test strategy document presents an opportunity to review the test plan with the project team.

Reason number 5: The test strategy document describes the roles, responsibilities, and the resources required for the test and schedule constraints.

Reason number 6: When we create a test strategy document, we have to put into writing any testing issues requiring resolution (and usually this means additional negotiation at the project management level).

Reason number 7: The test strategy is decided first, before lower level decisions are made on the test plan, test design, and other testing issues.

阅读全文 »

Share This

这个题目来源于上周六在广州软件测试交流会的一个主题，pent老弟介绍了他的一个简单但是非常有效的架构。说这个架构简单是因为结果非常简单，除了任务定制，调度之外，没有其他多余的功能，说有效或者强大是因为他实现了一个强大的自动化测试回归机制，系统虽小，该有的功能都有的。这个架构分四个部分：
每日构建（daily build）-》部署（deploy）-》冒烟测试（smoke test）-》结果报告

四个部分是是一个完整的整体，对于有些项目来说，其他中的第二个步骤部署可能不一定是必须的。
先说每日构建，这对于一个产品的研发特别是协同开发的产品来说，是特别重要的一个缓解，而且在很多公司已经形成一个良好的机制，每天下班时间，系统自动根据配置管理进行每日构建，大大节省了研发的时间。
阅读全文 »

Share This

Q: What if there isn’t enough time for thorough testing?

* Which functionality has the largest safety impact?
* Which functionality has the largest financial impact on users?
* Which aspects of the application are most important to the customer?
* Which aspects of the application can be tested early in the development cycle?
* Which parts of the code are most complex and thus most subject to errors?
* Which parts of the application were developed in rush or panic mode?
* Which aspects of similar/related previous projects caused problems?
* Which aspects of similar/related previous projects had large maintenance expenses?
* Which parts of the requirements and design are unclear or poorly thought out?
* What do the developers think are the highest-risk aspects of the application?
* What kinds of problems would cause the worst publicity?
* What kinds of problems would cause the most customer service complaints?
* What kinds of tests could easily cover multiple functionalities?
* Which tests will have the best high-risk-coverage to time-required ratio?

Q: What if the project isn’t big enough to justify extensive testing?
阅读全文 »

Share This

Q: What makes a good QA engineer?

A: The same qualities a good test engineer has are useful for a QA engineer. Additionally, Rob Davis understands the entire software development process and how it fits into the business approach and the goals of the organization. Rob Davis’ communication skills and the ability to understand various sides of issues are important. Good QA engineers understand the entire software development process and how it fits into the business approach and the goals of the organization. Communication skills and the ability to understand various sides of issues are important.

Q: What makes a good QA/Test Manager?
阅读全文 »

Share This

Q: Why are there so many software bugs?

A: Generally speaking, there are bugs in software because of unclear requirements, software complexity, programming errors, changes in requirements, errors made in bug tracking, time pressure, poorly documented code and/or bugs in tools used in software development.

* There are unclear software requirements because there is miscommunication as to what the software should or shouldn’t do.

* Software complexity. All of the followings contribute to the exponential growth in software and system complexity: Windows interfaces, client-server and distributed applications, data communications, enormous relational databases and the sheer size of applications.

* Programming errors occur because programmers and software engineers, like everyone else, can make mistakes.

* As to changing requirements, in some fast-changing business environments, continuously modified requirements are a fact of life. Sometimes customers do not understand the effects of changes, or understand them but request them anyway. And the changes require redesign of the software, rescheduling of resources and some of the work already completed have to be redone or discarded and hardware requirements can be effected, too.

* Bug tracking can result in errors because the complexity of keeping track of changes can result in errors, too.
阅读全文 »

Share This