Webinar: Investment for Testing, How and Where?

Thứ sáu này rồi, hên quá mới vừa biết trước 1 ngày, vẫn còn kịp. Presenter là Mr. James Whittaker from Microsoft, nhưng giờ mới qua Google làm rùi Director of Testing, ngầu quá xá.. 

If you were going to invest more money in testing, where would you place those bets? Testing early in the cycle? Automation? Manual testing? Better requirements and planning? Better documentation? Torture devices for your devs?

In our latest uTest webinar, More Bang For Your Testing Buck, best-selling author James Whittaker will take a critical look at how to maximize your investments in testing, including an examination of the tools, best practices and methodologies that can help make testing a “happier place.”

The webinar is schedule for Friday, December 10 at 11:00 AM (EST). 
(Thứ sáu tuần này lúc 11h00 PM Friday, VN Time)

Register now at Go-To Meeting >>>>

As the former Test Architect at Microsoft and the current Director of Testing at Google, James is one of the most accomplished professionals in the testing business. Long-time readers of our blog will know that he is also no stranger to the uTest community.

Here are a few of the uTest projects he’s participated in:

Webinars
The Future of Software Testing
5 Ways To Revolutionize Your QA
Exploratory Software Testing (<

eBooks
5 Ways To Revolutionize Your QA

Interviews
Testing the Limits – Part I (2009)
Testing the Limits – Part II (2009)
Testing the Limits – Part I (2010)
Testing the Limits – Part II (2010)

»»  read more

Tài liệu PDF tại ASTA 2010

Hội nghị ASTA 2010 là Hội nghị về Kiểm thử Phần mềm "quốc tế" được tổ chức vào ngày 05/11/2010 do HP support và VTB host diễn ra tại ĐH Hoa Sen, TPHCM. Vé vào cửa: FREE

Mục đích hội nghị (theo như quảng cáo là):

    * Chia sẻ kinh nghiệm, chuyên môn và những kiến thức thực tiễn tốt nhất trong lĩnh vực kiểm thử phần mềm
    * Trình bày cách sử dụng của một vài công cụ kiểm thử tự động
    * Nắm bắt những kỹ năng liên quan đến kỹ thuật kiểm thử cơ bản và nâng cao
    * Thu thập kiến thức về những hệ thống kiểm thử khác nhau chẳng hạn như khách hàng/ công ty, những ứng dụng web, những hệ thống thời gian thực tế và hệ thống ghi nhớ.
    * Hiểu được tâm lý trong kiểm thử phần mềm
    * Hiểu được chiến lược kiểm thử và kế hoạch quản lý kiểm thử hiệu quả
    * Hiểu được kiểm thử liên quan đến ma trận và đo lường.

Speakers đến từ nhiều nước Asian như Singapore, Malaysia, Japan, có 1 ông Ấn Độ nhưng ko đến được do airplane issue. "Đặc biệt" có bài keynote của 1 mister nhà nước, ông Ng.H.Quốc, thuộc eGov của Bộ thông tin truyền thông, đáng tiếc là bài phát biểu quá sơ sài nếu ko nói quá dỡ, chả chuyển tải được thông tin gì.. FREE mà, ko trách. Còn những bài chuyên môn thì như thường lệ room của Mr. Jung là dzui nhất. Mr. Ngoc Tú lại được xếp vào giờ ăn trưa (12h30), nên làm vội vội vàng vàng,  mức độ react của audience cũng hạn chế vì đói bụng quá, ai cũng muốn cho xong để đi ăn.

Nói chung là OK. Download tài liệu PDF (21MB) của hội thảo:
http://www.mediafire.com/?ya0wm10g12e3ev9

Nội dung bao gồm: 

- Automation Third Party Controls
- Continue Testing
- Defect Target Metrics
- Engineering in Software Quality and Testing
- Establishing Test Defect Prediction Model Using
- How to apply Pairwise Techniques in real
- Mastering the Application Lifecycle
- Performance Testing for SOA Web Applications using Test Driven Development
- Software Security Testing Best Practices
- Software Testing Tools for Automated Testing with Special Reference to HP QuickTest Professional
- Surviving Disability @508
- Testing Skills
- Transforming IT Application

»»  read more

Webinar: 5 Ways To Revolutionize Your QA

There are Better Ways to Manage the QA Process ??? James Whittaker will prove it

Dr. James Whittaker - the man who wrote the book on software testing - will be joining us for another uTest webinar on Tuesday, March 31 (1PM - 2PM ET). Here, you’ll learn five key insights that will challenge your perceptions of QA management, including:

* The key difference between "experience" code and "infrastructure" code

* Why testers should play a greater role in development

* Why testing sometimes sucks

Register now and receive a free copy of his latest e-book!


=====================================
Update Apr-2: There are 5 insights in the webinar he think it will revolutionize theway we test and make QA team more effective, let's see what it is:

- Insight 1: There are two types of code and they require different types of tests
- Insight 2: Take your testing down a level from features to capabilities
- Insight 3: Take your testing up a level from test cases to techniques
- Insight 4: Improving development is your top priority
- Insight 5: Testing without innovation is a great way to lose talent

For more detail download the PDF here

Or here:

»»  read more

My interview questions last time

Long time no writing English, try this entry... I would just like come back a little time last year with my interview at several company. Many interesting things came up, certain matter to think. Here below are just 3 questions I remembered that most company asked. And the answer is just my own idea if I am being asked again.

Here they are:

1. Describe one example where your actions led to improved quality of your organization's product or service.

Well, before, as a QC, I have to write test case for each feature, of course, but there was no peer-meeting to review test case before implementing-phase. What I suggest to do is we should have a meeting (in at least 1 hours) with developers to go through the potential business or test cases (not all). During the meeting, I will keep asking question about ambiguous place in requirement for people discussion until it's clear enough for implementation. The priority of this meeting to make sure all or most of requirements can be: (1) measurable, (2) clear & consistent, and optional is to find missing requirements if any.

2. Describe your actions from the time you receive a task to get it done. What make you think that you can control and release it on time with good quality?

>> Yup, QC must care about quality, of course, but on time also very important. It's not very easy to balance it. And this is my point of view, the factors made me confident to deliver task done with good quality and on time are:

+ My technical skill related to this task.
+ The requirement or spec should be clear and understandable.
+ Last but not least, time constraint of course.

3. While a new feature is implementing, you keep receiving some new requirements what do you do to handle it?

>> OK easy :), let's presume that I am working on a product of company not the outsource. First (1)What it is! I study it and note it down, then (2)Question it! I will ask myself if it is really necessary to put in current milestone or sprint. And think about the top risk to have this implemented. Discuss it, then put this change request item to product backlog or somewhere whatever, just a place to store the changes, not at the time but during implementation phase and, (3)Keep track it, talk to dev to figure out the impact if any, based on that go straight to update the test case of related feature. Finally, test it over not only itself but also its parent features.

--------------------------------------------
That's all for now. Actually, there are more questions interesting than this. I will go back to share it later :)

»»  read more

Tool chụp màn hình cho Tester

Là Tester bạn không thể không nghe đến cụm từ "chụp màn hình", đó là 1 cách một làm cho bug report của mình dể hiểu hơn, đẹp đẽ hơn. Không chỉ giúp ích cho lead, customer, dev hiểu đúng vấn đề, nó còn giúp mình hay một tester khác lúc làm regression nữa. Nói chung nó rất helpful trong cuộc đời 3 chìm 7 nổi của Tester :). Entry này mình chia sẽ lại vài tool mình đã "nghiệm" qua từ hồi còn chân ướt chân ráo làm "chuyên viên kiểm nghiệm phần mềm" đến nay, cũng là vài phút tri ân cái "nồi cơm" của mình cho entry về testing đầu tiên của năm 2009...

1/ Print Screen + Paint Brush: một thời oanh liệt

2/ Kleptomania: một cái tên lạ hoắc, giờ chắc ko ai xài nữa
http://www.structurise.com/kleptomania/

Tool này giúp lấy text ra từ một dialog hay một window bất kỳ mà "triển chuột" ko sờ tới để Ctrl+C được. Mình xài nó từ hồi 2005, version 2.6, năm nay 2009 coi lại cũng vẫn là 2.6, pó tay. Tool hay nhưng còn lỗi nhiều quá, kẹt lắm mới xài tới

3/ Ctrl + Alt + Ins: copy text từ một dialog chuẩn

Nếu ko muốn dùng Kleptomania thì đây, tổ hợp phím tắt này có thể dùng mọi lúc mọi nơi :). Nó hay vậy nhưng cũng có ít ng biết, đã có lần nó giúp mình impress anh em Expert trong một seminar đầu tiên ở Agile Mobile :)

Eg: Text này copy được từ chương trình Notepad++, khi đóng một tab mà chưa kịp save content
---------------------------
Save
---------------------------
Save file "new 3" ?
---------------------------
Yes No Cancel
---------------------------

4/ Snipping Tool: built-in of Vista



Tool này bình thường ko xuất hiện trên menu by default, mình phải lôi nó ra, just enter "Snip" in the "Star Search" sẽ thấy ngay. Khá hơn Print Screen vì nó cho phép mình cắt "một khúc" màn hình và có và công cụ thô sơ để highlight một số khu vực mong muốn, nhưng tiếc là không type chữ được. Khi mình dùng tool này lúc nào cũng phải Copy qua Paint làm thêm xí nữa.

5/ Firefox add-in: Screen grab: cuộn để chụp toàn bộ trang web



Nếu bạn muốn chụp hết một trang web thì phải làm sao, hồi xưa mình đã từng "ngu dại" chụp 2-3 lần rồi paste vô Paint cắt cắt - dán dán nhưng từ hồi có tool này là phẻ re. Sau khi install add-in này xong, xài rất đơn giản. Muốn chụp trang nào chỉ việc open Firefox with that URL then click chuột phải chọn menu Screen Grab thế là xong.

Update Feb-20: Tương tự add-in này còn có Fireshot, tool này đầu tư nhiều hơn có cả Editor hình riêng nữa. Có bản free và bàn thương mại, install tại đây

6/ Snag it (version 9.0). Download here (20mb)



Gã này là đại gia rồi, ai cũng biết. Có đủ đồ chơi hết, gồm tất cả công dụng của 5 tool nói trên, cắt trang web dài, copy text from a dialog, hoặc 1 object bất kỳ đang trên màn hình. Hiện tại mình dừng lại ở em này. Vì chưa thấy tool nào qua mặt được nó.

Update June-12-09: bản portable mới nhất ko cần install, ko cần crack

Hope it's helpful to all my dear friends. Happy Testing :)

»»  read more

Interesting articles of Cem Kaner

After I visited Kaner site at the end of 2007 (the jobless time), I got an idea to categorize them all one day. And it's time these days. I started collect the "high-light" articles since last week and the last small piece will be done today, Sunday. It will be a tool to help me to access these slides easier later, and I hope it would be interesting for you too, my dear testing friends.

To get ALL pdf files of Kaner's article, just come here to download it, one 81M-zip file.

(Here is the latest one in his site when I downloaded ALL of them on 2008-10-30
Cem Kaner, "Comments on the August 31, 2007 Draft of the Voluntary Voting System Guidelines." Submitted to the United States Election Assistance Commission, May 2008.)

+ Testing in general

- Cem Kaner, "What is a software defect?" Software QA, Volume 3, #6, 1996.
- Cem Kaner, "Bad software—Who is liable?" (Invited address) Proceedings of the American Society for Quality's 52nd Annual Quality Congress, Philadelphia, May, 1998.
- Cem Kaner, "What is a good test case?" [SLIDES] Software Testing Analysis & Review Conference (STAR) East, Orlando, FL, May 12-16, 2003.
- Cem Kaner, "Fundamental challenges in software testing." [SLIDES] Colloquium Presentation at Butler University, April 2003.
- Cem Kaner & James Bach, "Black box software testing: Tutorial on test design." [SLIDES] (Tutorial) Pacific Northwest Software Quality Conference, Portland, OR, October 13-15, 2003.

- Cem Kaner, "Notes for the Workshop on Combination Testing." [SLIDES] Workshop on Combination Testing, Seattle, WA, January 2006.
- Sowmya Padmanabhan, Domain Testing: Divide & Conquer [Appendices] Unpublished M.Sc. Thesis, Florida Institute of Technology, Melbourne, FL, 2004. 
- Cem Kaner, "Requirements for test documentation." (Invited address) Quality Assurance Institute Annual International Quality Conference, Orlando, FL., September, 1999.
- Cem Kaner & James Bach "Developing the right test documentation." [tutorial] 14th International Software Quality Conference (Quality Week), San Francisco, CA, June, 2001. Also presented at Pacific Northwest Software Quality Conference, Portland, OR, October, 2001.
- Cem Kaner & James Bach, "Exploratory testing in pairs." [SLIDES] Software Testing Analysis & Review Conference (STAR) East, Orlando, FL, May, 2001. Also presented at Software Testing, Analysis & Review Conference (Star) West, San Jose, CA, October, 2001.
- Cem Kaner, (2002) "Effective bug reporting." [SLIDES] (Tutorial session) 15th International Software Quality Conference (Quality Week), San Francisco, CA, September, 2002.
- Cem Kaner, (2002) "Paradigms of black box software testing." [SLIDES] (Tutorial session) 15th International Software Quality Conference (Quality Week), San Francisco, CA, September, 2002.
- Cem Kaner, "The context-driven approach to software testing." [SLIDES] (Keynote address) Software Testing Analysis & Review Conference (STAR) East, Orlando, FL, May, 2002.
- Giri Vijayaraghavan & Cem Kaner, "Bug taxonomies: Use them to generate better tests." [SLIDES] Software Testing, Analysis & Review Conference (Star East), Orlando, FL, May 12-16, 2003. (Received the Best Paper Award at STAR).
- Cem Kaner, "Bug Advocacy." [SLIDES] July, 2000.
 

+ Exploratory testing 


- Andy Tinkham & Cem Kaner, "Learning styles and exploratory testing." [SLIDES] Pacific Northwest Software Quality Conference, Portland, OR, October 13-15, 2003.

- Andy Tinkham & Cem Kaner, "Exploring exploratory testing." [SLIDES] Software Testing Analysis & Review Conference (STAR) East, Orlando, FL, May 12-16, 2003.

- Cem Kaner, "A tutorial in exploratory testing." [SLIDES] QAI QUEST Conference, Chicago, April 2008
- Cem Kaner, "The Nature of Exploratory Testing," [SLIDES] Choices in IT conference. Columbus, OH, September, 2006.
- Cem Kaner, "Exploratory testing after 23 years." [SLIDES] [Keynote address] Conference of the Association for Software Testing, June 6, 2006.
- Cem Kaner, "Exploratory Testing." (Keynote address) [SLIDES]. Quality Assurance Institute Worldwide Annual Software Testing Conference, Orlando, FL, November 2006.
- Cem Kaner, "Developing Skills as an Exploratory Tester." (Tutorial) [SLIDES] Quality Assurance Institute Worldwide Annual Software Testing Conference, Orlando, FL, November 2006.
- Cem Kaner & James Bach, "The nature of exploratory testing." [SLIDES], Tampere, Finland, May 7, 2004.

+ Automation Test


- Cem Kaner, Walter P. Bond & Pat McGee, "High volume test automation." [SLIDES] (Keynote Address) Software Testing Analysis & Review Conference (STAR) East, Orlando, FL, May 20, 2004.
- Cem Kaner, "Avoiding shelfware: A manager's view of automated GUI testing." [SLIDES] (Keynote address) Software Testing Analysis & Review Conference (STAR) East, Orlando, FL, May 6, 1998.  

- Pat McGee & Cem Kaner, "Experiments with high volume test automation." Workshop on Empirical Research in Software Testing, International Symposium on Software Testing and Analysis, Boston, MA, July 2004. 
- Cem Kaner, Walter P. Bond & Pat McGee, "High volume test automation." [SLIDES] (Colloquium) Florida Institute of Technology, Melbourne, FL, October 31, 2003. (The slides are also a preview of my keynote address at STAR East 2004 on high volume test automation.)
- Cem Kaner, "Software test automation: A real-world problem." (Colloquium) Allegheny College, Meadsville, PA, 1999.
- Cem Kaner, "GUI regression automation." Washington Software Association QA SIG, Redmond, WA, May 20, 1997.
- Cem Kaner, "Improving the maintainability of automated test suites." Software QA, Volume 4, #4, 1997. (Also published in Proceedings of the 10th International Software Quality Conference (Quality Week), San Francisco, CA, May 28, 1997.)
- Cem Kaner, "Architectures of test automation." [SLIDES] Software Testing, Analysis & Review Conference (Star) West, San Jose, CA, October, 2000.

+ Industry

- Cem Kaner, "The ongoing revolution in software testing," [SLIDES] October 2007,  [2004 version]
- Cem Kaner, "Software testing as a social science," [SLIDES] STEP 2000 Workshop on Software Testing, Memphis, May 2008.
- Robert L. Glass, Ross Collard, Antonia Bertolino, James Bach, & Cem Kaner, "Software testing and industry needs," [OUT-LINK] IEEE Software, vol. 23, pp. 55-57, 2006.
- Cem Kaner, "Software testing as a social science." [SLIDES] Canadian Undergraduate Software Engineering Conference (CUSEC 2006), Montreal, Canada, January 19-21, 2006. More recent versions are Colloquium at Dalhousie University, May 2006; Toronto Association of Systems and Software Quality, October, 2006.
- Cem Kaner, "Software testing as a social science." [SLIDES] IFIP Working Group 10.4 meeting on Software Dependability, Siena, Italy, July 6, 2004.
- Cem Kaner, "The past and future of software testing." [SLIDES] Software Testing Day, Tampere University of Technology, Tampere, Finland, May 4, 2004.
- Cem Kaner, "An outline for software testing outsourcing." [SLIDES] Software Testing Analysis & Review Conference (STAR) East, Orlando, FL, May 2000.
 
+ Coverage/Metrics

- Cem Kaner "Rethinking software metrics: Evaluating measurement schemes." Software Testing & Quality Engineering. Vol. 2, Issue 2 (March) p. 50-57, 2000.
- Cem Kaner, "Software-related measurement: Risks and opportunties," [SLIDES] October 2007
- Cem Kaner, "Improve the power of your tests with risk-based test design." [SLIDES] QAI QUEST  Conference, Chicago, April 2008
- Cem Kaner, "Software negligence and testing coverage." (Keynote address) Software Testing, Analysis & Review Conference (STAR), Orlando, FL, p. 313, May 16, 1996.
- Cem Kaner, "Fundamental issues in software metrics." [Tutorial] Canadian Undergraduate Software Engineering Conference (CUSEC 2006), Montreal, Canada, January 19-21, 2006
- Cem Kaner & Walter P. Bond, "Software engineering metrics: What do they measure and how do we know?" 10th International Software Metrics Symposium (Metrics 2004), Chicago, IL, September 14-16, 2004.
- Cem Kaner, "Software negligence and testing coverage" (updated). Software QA Quarterly, Volume 2, #2, p. 18, 1995.
- Cem Kaner, "Test planning for consumer software." Quality Week Conference, San Francisco, CA 1988.
- Cem Kaner & James Bach, "Rapid test planning." [SLIDES] Software Testing, Analysis & Review Conference (STAR) West, San Jose, CA, October, 2001.
- Cem Kaner, "Testing undocumented software under impossible deadlines." [SLIDES] Software Testing, Analysis & Review Conference (STAR West, San Diego, CA, October 30, 1998; also at Software Testing, Analysis & Review Conference (STAR) East, Orlando, FL, May 1999.
- Cem Kaner, "A short course in metrics and measurement dysfunction." [SLIDES] (Tutorial session) 15th International Software Quality Conference (Quality Week), San Francisco, CA, September, 2002.
- Cem Kaner, "Measurement issues and software testing." [SLIDES] (Keynote address) Proceedings of the QUEST 2001 Segue Software User's Conference, Orlando, FL, April 2001.
- Cem Kaner, "Measurement of the extent of testing." Pacific Northwest Software Quality Conference, Portland, OR, October, 2000.

+ For Lead/Manager:

- Cem Kaner, "Measuring the effectiveness of software testers." [SLIDES] in Progressive Insurance. Cleveland, OH, 2006; [2002 version]

- Cem Kaner, "How many lightbulbs does it take to change a tester?" [SLIDES] (Keynote address) Pacific Northwest Software Quality Conference, Portland, OR, October 13-15, 2003.

- Cem Kaner, "Interviewing software testing job candidates." 12th International Software Quality Conference (Quality Week), San Jose, CA, May, 1999.
- Cem Kaner & David Pels, "Collaboration between support staff and testers." [SLIDES] Proceedings of the Support Services Conference & Expo, San Francisco, September 9, 1998.
- Cem Kaner, "Recruiting software testers." (version 6) Software Testing Analysis & Review Conference (STAR) West , San Jose, CA, May 2000. [1999, 1st version] [version 4a]
- Cem Kaner, "Negotiating testing resources: A collaborative approach." 9th International Software Quality Conference (Quality Week), San Francisco, CA, May, 1996.
- Cem Kaner, Elisabeth Hendrickson & Jennifer Smith-Brock , "Managing the proportion of testers to (other) developers." [SLIDES] Pacific Northwest Software Quality Conference, Portland, OR, October, 2001. (Essentially the same paper was presented at 14th International Software Quality Conference (Quality Week), San Francisco, CA, June, 2001.)
- Cem Kaner, "Inefficiency and Ineffectiveness of Software Testing: A Key Problem in Software Engineering." National Defense Industrial Association Workshop: Top 5 Software Engineering Problems or Issues Prevalent Within the Defense Industry, Washington DC, August, 2006.
- Cem Kaner, "Contracts for testing services: Warranty and indemnification." Software QA, Volume 3, #5, p. 20, 1996.
- Cem Kaner & Michael Kurtz, "Software contracting: Proposed revisions to the UCC." [SLIDES]
- Cem Kaner, "Contracts for testing services: Settling disagreements." Software QA, Volume 4, #2, 1997.
- Cem Kaner & David Pels, "Software customer dissatisfaction." Software QA, Volume 4, #3, p. 24, 1997.
- Cem Kaner, "Looking for your first job in software testing." [SLIDES] Talk at Florida Tech, 2002.
- Cem Kaner, "Don't use bug counts to measure testers." Software Testing & Quality Engineering, May/June, 1999, p. 80.
- Cem Kaner, "The role of testers in XP." [SLIDES] Initially on flipcharts at a workshop at the Agile Development conference, Salt Lake, UT, June, 2003. On slides at Bay Area XP meeting, Palo Alto, CA, August 2003.
- Cem Kaner, & James Bach (2002) "Developing your testing approach: A context-driven analysis." [SLIDES] (Keynote address) Rational User Conference, Orlando, FL, August 2002.
- Cem Kaner & Brian Lawrence, "Software Test Managers' Roundtable." (Meeting handbook), Software Test Managers' Roundtable, October 2000.Cem Kaner & Johanna Rothman, "Managing testing resources: Five suggestions for the project manager." PMI ISSIGreview, Vol. 10, Number 4 (October), 2000.
- Brian Marick, James Bach & Cem Kaner, "A manager's guide to evaluating test suites." 13th International Software Quality Conference (Quality Week), San Francisco, CA, June, 2000.

+ Training 

- Cem Kaenr, "BBST: Evolving a course in black box software testing." [SLIDES] BBST Project Advisory Board Meeting, January 2008
- Cem Kaner. "Teaching testing: A skills-based approach." [SLIDES] 14th International Software Quality Conference (Quality Week), San Francisco, CA, June, 2001.

- Cem Kaner & Sabrina Fay, "Teaching the black box testing course." Poster session, Conference of the ACM Special Interest Group on Computer Science Education (SIGCSE 2004), Norfolk, VA, March 3-7, 2004. 
- Cem Kaner & Tim Coulter, "Creating an Open Certification Process,"Faculty Poster Session [POSTER page 1 page 2], Conference of the ACM Special Interest Group on Computer Science Education (SIGCSE 2007), Covington, KY, March 2007.

- Cem Kaner, "Career development, education, training and certification." [SLIDES] Presentation at Progressive Insurance, July, 2006.
- Cem Kaner, "Teaching software testing." [SLIDES] Presented at a meeting of Finnish University teachers of software testing, at the Tampere University of Technology, Tampere, Finland, May 5, 2004.
- Cem Kaner & Sowmya Padmanabhan, "Practice and transfer of learning in the teaching of software testing,"
- Cem Kaner, "Developing software testing courses for your staff" (Tutorial) [SLIDES] in Pacific Northwest Software Quality Conference, Portland, OR, October 2006. 
- Cem Kaner, "Open courseware and open certification in software testing," [SLIDES] Conference of the Indianapolis Quality Assurance Association, October, 2006.
[SLIDES] Conference on Software Engineering Education & Training, Dublin, July 2007. 
- Cem Kaner, "Creating Your Own In-House Software Testing Course." [SLIDES] Conference of the Association for Software Testing , Indianapolis, OH, June 2006.
- Andy Tinkham & Cem Kaner, "Experiences teaching a course in programmer testing." Agile 2005 Converence, Denver, CO, July 2005.
- Cem Kaner & Rebecca Fiedler, "Blended learning: A software testing course makeover." 11th Sloan-C International Conference on Asynchronous Learning Networks, Orlando, FL, November 2005. 
- Cem Kaner & Rebecca Fiedler, "Adaptation & Implementation of an Activity-Based Online or Hybrid Course in Software Testing." Proposal to the National Science Foundation. Submitted January 10, 2007.
- Cem Kaner, "Teaching the software testing course." (Tutorial session) Conference on Software Engineering Education & Training 2004, Norfolk, CA March 3-7, 2004.
- Cem Kaner, "Teaching domain testing: A status report." [original, longer draft] Conference on Software Engineering Education & Training 2004, March 1-3, 2004.
- Cem Kaner, "Assessment in the software testing course." [SLIDES] Workshop on the Teaching of Software Testing (WTST), Melbourne, FL, February, 2003.

»»  read more

The Future of Software Testing

Join Dr. James Whittaker, Software Architect at Microsoft and renowned software testing expert, as he presents next uTest webinar - The Future of Software Testing.

For this webinar, James will be extending on his outstanding series of blog posts about the software testing of tomorrow. As one of the world's top software testing experts, James is uniquely positioned to understand the role of testing today and how it will impact software test and development tomorrow. His vision of the future has ranged from the rise of crowdsourcing to the greater role of testers as designers.

Register here: https://www2.gotomeeting.com/register/313938344

Thursday, November 20, 2008 1:00 PM - 2:00 PM EST
(12h midnight VN-time)

As an added bonus, we will be giving away ten copies of James Whittaker's books on software testing, including How to Break Software: A Practical Guide to Testing. Anyone who attends the webinar is eligible to win! Simply sign up and make sure you attend on November 20.

(I will update the webinar slide later on)

>> Ah I remember I've seen that book (How to break software) in LTRC's library when I looked for some book other than "Testing Computer Software"

>> Recently, I just read a PDF on Cem Kaner's site about same topic: The ongoing revolution in software testing that point out major changes of the industry since 1990's and predict what will be in the future

Here is the last summary slide fyi:

click here to download PDF file

»»  read more

Boost Your Testing Process - Free Webinar

Software testing is a complex process, so we wanted to put together a webinar that could help you make sense of all the challenges.  When you’re finished, you’ll learn some of the best practices for managing a testing process, getting the most from your testing team, and making sure your testing is working for you.

In particular, you will learn how to:

    * Define your testing process
    * Start test design during the requirements process
    * Build a useful testing matrix
    * Perform regression testing that is based on impact analysis
    * Collect simple measurements for process improvement and reporting

If you are interested in this, let's go here for register. Last time uTest host webinar about "Agile Testing" very good, even they also advertise themselves a bit. The information is useful, and attendance no need to have Voip telephone for sound, speaker is Ok . The sound quality is quite good (that time is 11h PM), you can also put the question into a small textbox. I tried to put one and got back the answer. But you can't make question by your mic :). But that's enuogh convenience to me. It's FREE by the way. (And here if you want spend money go to this seminar about Estimation in software industry, present by a Vietnamese but the fee is in dollars $260 :P)

That's it! I will continue join this webinar again.

»»  read more

Security Testing

Security Testing these days is hot job in testing career path, it would makes you different and special one among Testers. I'd love to learn this particular topic if I have chance. For now, to understand what is security testing, now we just look at a glance the 1250 EUR course of Security Testing that I collect from testingexperience.com.

----------------------------------------------------
1. What is application security
• What does Application Security deals withBest practices •
2. SDL – Security Development Life Cycle and Threat modeling
• Threats and vulnerabilities •
• The STRIDE categories •
• Creating a threat model •
• The SDL methodology •
3. Writing a security test plan
• How to write security test cases •
• How to set up security testing programs (and how they are different from standard testing)
• OWASP testing best practices •
4. Web technologies & security Technologies
• Http & TCP •
• Servers & Proxies •
• Encryption and Hashing •
• SSL & Digital signatures •
• Authentication Technologies •
• XML WS standards •
5. Common attacks & Demos
• OWASP top ten •
• Buffer Overrun •
• SQL Injection •
• Cross Side Scripting XSS •
• Denial Of Service (many types) •
• Back Doors •
• Spoofing •
• Forceful Browsing & Flow Bypassing •
• Parameter Manipulation •
• Information Disclosure •
• One Click Attack •
• Session Hijacking •
• Cookie Poisoning •
• Directory Traversal •
6. Security Testing Methodologies
• Fuzzing •
• Penetration Testing •
Static / Dynamic analyzing •
7. Testing execution
• Discovery phase •
• The testing checklist •
• Attacks simulation Tools and methods •
  ◦ Discovery tools ◦
  ◦ Http Proxies ◦
  ◦ Fuzzing tools ◦
  ◦ Crackers (Brute force, Hashing ) ◦
  ◦ Scanners ◦
• How to choose the correct tool – Tools evaluation
• Explain about security code review •
8. Web Services
• WS basics •
• Networking Attacks simulation tools and methods
• Federation – check the identity system •
9. Documentation
• How to write a security report •
• Mitigations •
10. Lab
• In the Lab the students will test a live demo site using the tools and methods they learned in the class.
• The students will experience all the common web application attacks.

(Source SecurityTesting_kurz.pdf)

===========================================
Update July-12-2009:

Download this particular e-magazine specialized for Security Testing
testingexperience02_09 (June-2009) - 11MB - PDF file


===========================================
Security Testing Tips

(Update May-18-2008)

Although it’s a broad term, security testing can be broken down into six basic concepts:  Availability, Authentication, Authorization, Confidentiality, Integrity and Non-repudiation. I’ll define each concept briefly, however, I encourage you to research each concept for a better understanding.

    * Availability: Assuring that information & communications services are available and maintained for authorized persons when needed.
    * Authentication: Assuring the validity of any type of originator, transmission or message.  This also gives confidence that information is received by a known and validated source.
    * Authorization: Assuring that an individual can allow/deny access to a system/service/operation (e.g. Access control).
    * Confidentiality: Ensuring information is accessible only for those with authorized access and to prevent information disclosure to any party other than the intended recipients. Often ensured by encoding information using algorithms (cryptography).
    * Integrity: Ensuring received information is preserved successfully with no alteration.
    * Non-repudiation: Ensuring action/communication cannot later be denied (usually used by form of authentication and time stamping).

Security Testing Methods:

There are 3 types of testing methods which involve various sets of attacks: Information/system gathering, logical, and injection attacks. Each are used for specific testing results, however various attacks share the same security concepts, and are therefore quite similar to one another.

Information gathering (i.e. system related) attacks

    * Client-side source code analysis
    * Application reconnaissance
    * Error messages analysis
    * Directory traversal

These methods include various types of information gathering from a web application/server by means of source code and error message analysis, exposure of directory structure or other attacks which results in information exposure. Here are they are in no particular order:

Logical Attacks

    * Cookie poisoning
    * Parameter tampering
    * Flow bypassing
    * Direct access of components files
    * Session hijacking
    * Penetration testing
    * Buffer overflow

These methods relate to various logical attacks which may be executed both manually or via specific tools/scripts. Logical attacks are more sophisticated and thus more interesting & challenging to the tester, who needs to have a good understanding of information technology and specific knowledge of cookies, POST/GET requests & parameters, etc.

Injection Attacks

    * SQL injection
    * Cross Site Scripting (XSS)
    * Scripts injection

These methods relate to various scripts & SQL commands injections into web application forms and are the most common attacks, yet they are both serious and dangerous. Detecting such vulnerabilities in early stages of development can prevent unnecessary flaws.

In my next blog post, I will address some common (and some not-so-common) tools that can make security testing easier and more productive for testing engineers of all experience levels.

In the meantime, happy testing!

Bernard Lelchuk 
Bug Battle winner

Source: Blog uTest.com

»»  read more

ISTQB trial test for FREE

I'm going to take ISTQB trial examination next Sunday on Sep-26. I have had to come to the office for registration by hand (yesterday). Thanks to VTB so that I can try the test first before get into real one.

One thing luckily from Agile Mobile, they will support exam-fee for employee taking any certificate in advance. Great deal isn't it! :)

Come to the address below for registration taking the ISTQB trial test, the office's available for you till 9h o'clock PM everyday (not Sunday) and receptionist overthere, she is so kind and very nice ;).

>>> It's completely FREE (for Foundation level only)

Viện Công Nghệ Thông Tin & Quản Trị Tài Chính.
195 đường D2, Văn Thánh Bắc, Phường 25, Quận Bình Thạnh, TP. HCM
Điện thoại: (08) 803 5020; (08) 512 7652; 

Go to this link at VTB to learn more about this FREE test. Hurry up, next month will be on Oct-31.

>>> Here is the agenda for this trial context within 2 hours

- 10' : Instruction of studying ISTQB
- 10' : About ISTQB Certificate of Foundation level and its glossary.
- 10' : Structure and process of the test
- 60' : Trial time in the real test sample for Foundation Level
- 30' : The result and questions.

P/S: Here are these books need to go over before come to the test:
1/ Syllabus Foundation (Level 1 - Foundation)
2/ CTAL_Syllabus_V_2007 (Level 2 - Advanced)
3/ Glossary

-------------------------------------
About ISTQB and VTB
1/ ISTQB - Chứng chỉ quốc tế cho Tester
2/ Think hard before coming to VTB for Testing course

=========================
Update Oct-3: Full sample of the test from a person named Vân who just joined the test on Sep-26, click here for the test (if the link down, please see my comment)

»»  read more

10 tips for successful testing! [magazine]

Software development is often a balanced exercise in time and quality management. For most companies it is a constant  struggle to complete  tasks on  time and within budget, usually resulting in quality being neglected. When  applications are finally released into production, users are often confronted with only basic functionalities or even the complete omission of  functionalities due to the lack of development time.

How do you set up or improve your software testing process to reduce the business risk of poor application implementation? Here are a few simple tips to get you ahead in quality, saving you time and money:

1. Start early and be prepared!  
2. Select a testing method which fits your needs
3. Be objective 
4. Review, review, review, review … 
5. Prioritize 
6. Measure!
7. Know when to stop testing.
8. Preserve.
9. Communicate
10. Last but not least: keep it simple!

How do you think, it look simple doesn't it? Let's see this interesting article at Page 52 in latest update of magazine for testing pro from testingexperience.com, TE #3 can be download here (7MB)

+ For TE #2 download here
+ For TE #1 download here

»»  read more

An Introduction to Software Testing [ebook]

This is a very quick shot of software testing that is advised to read preparing for an software testing interview. I got this book from software testing help, but the link seem not work any more. I'd just like to post it here to share with whom missed this interesting book over there. Click here to down load (43 pages), and here below is the TOC of the book:

An Introduction to Software Testing
by Nick Jenkins

INTRODUCTION

• The Need for Testing
• Different Models of Software Development
• Other Models of Software Development
• Testing in the Software Development Life Cycle

CONCEPTS OF TESTING

• The Testing Mindset
• Test Early, Test Often
• Regression vs. Retesting
• White-Box vs Black-Box testing
• Verification and Validation

FUNCTIONAL TESTING

• Alpha and Beta Testing
• White Box testing
• Unit, Integration and System testing
• Acceptance Testing
• Test Automation

NON-FUNCTIONAL TESTING

• Testing the design
• Usability Testing
• Performance Testing

TEST PLANNING

• The Purpose of Test Planning
• Risk Based Testing
• Software in Many Dimensions
• Summary

TEST PREPARATION

• Test Scripting
• Test Cases

TEST EXECUTION

• Tracking Progress
• Adjusting the plan
• Defect Management

TEST REPORTING AND METRICS

• Software Defect Reports
• Root Cause Analysis
• Metrics

OTHER STUFF

• Release Control

PURE THEORY

• Complexity in Software

GLOSSARY

»»  read more

Hội thảo về Kiểm định phần mềm (16/9)

Tiếp theo năm trước, tháng 8/2007, lần này HCA tiếp tục host hội thảo này. Come on guys, let's go :)

* Hội thảo "Kiểm định chất lượng trong các công ty phần mềm"     

Đơn vị tổ chức:
- Hội Tin học TP.HCM (HCA)
- ICT Partnership

Buổi Hội thảo được tổ chức với mục đích nhằm chia sẻ kinh nghiệm về các mô hình quản trị chất lượng hiện đang được áp dụng tại một số công ty phần mềm, trao đổi về các vướng mắc thường gặp trong việc điều hành các hệ thống quản trị chất lượng, tạo điều kiện gặp gỡ trao đổi nghề nghiệp cho các anh em chuyên làm về quản trị chất lượng trong các công ty phần mềm.

Thời gian:

13h30 ngày 16/09/2008

Địa điểm:

Hội trường Saigon Times Club, 35 Nam Kỳ Khởi Nghĩa, Q.1, TP.HCM.

Liên hệ:
Vui lòng xác nhận tham dự  cho Văn phòng Hội Tin học TP.HCM (HCA) trước ngày 13/09/2008, gặp cô Lê Phương Khanh - Email: khanhlp@hca.org.vn hoặc hca@hcm.vnn.vn - Tel : 08.822 2876/ 273 6292/ 825 0053, Fax: 08. 825 0053.




(Source : hca.org.vn)

--------------------------------------------------------
Theo một nguồn tin tình báo nội bộ đáng tin cậy :) -là from Chaupk, ng rũ mình đi lần trước, thì Agenda của seminar lần này gồm:

1. Cty CSC Vietnam: Automation test experiences at CSC Vietnam
2. Cty GCS Vietnam: Training for testing engineer at GCS Vietnam
3. Cty PSD: Optimal Software Testing Solution.
4. Cty TÜV Vietnam: Main concerns of Test Manager
5. Cty TMA Solutions: Software Testing in Networking and Telecom domain


========================

Update on Sep-16-2008:

Nói thiệt, chả được gì nhìu, ko có gì mới. Agenda có chút thay đổi so với thông tin tình cáo, phần trong ngóng nhất là Test Telecom lại bị REMOVE điên chưa :(, Chắc TMA đã suy nghĩ lại, dấu nghề :)

Cái topic Testing Training của anh Toàn cũng hay, mà cái slide nào ảnh cầm mic là hội trường lại sôi động. (năm trước cũng vậy)

Một số hình ảnh: (cóp về từ web của HCA, ko có tấm nào dính mình :))

 Ngô Văn Toàn - GCS

Võ Phương Tâm - TUV

 

Mai Nguyễn - CSC 

Và đây là Agenda chiều hôm đó:

o Concerns of Software Testing Manager: Võ Phương Tâm (TÜV Rheinland Vietnam)
o Automation testing experiences: Mai Nguyễn (CSC Vietnam)
o Training for Testing Engineer: Ngô Văn Toàn (Global CyberSoft Vietnam)
o Metrics using in V&V projects: Nguyễn Trần Tùng (TMA Solutions)
o Optimal Software Testing Solution: Trần Thị Mỹ Dung (PSD)

>>> Download toàn bộ slide trên tại đây hoặc tại trang web của hca.org.vn

»»  read more

Making money with uTest

Today, the uTest MasterCard has come to my house by mail. This is not surprise at all, but last month I was when I got a professional support from Payoneer. Because I took the register to be a part-time Tester of uTest community in June not very serious, you know, just try to finish quick especially in some text box related to address, zip, phone,... (since I did not believe something like this, just nothing more than fun). Then one month later, an email sent from uTest remind me to activate the MasterCard. With a very clear instruction, I replied that I didn't know how to activate it, immediately 1 day after, a person name Pedor in Payoneer reply:

Our records indicate that the Payoneer card sent to you was returned by the post office.
In order for us to send you a new card, please reply to this e-mail and confirm your mailing address in the following format:

- Street Address Line 1:
- Street Address Line 2:
- City/State:
- Postal Code:
- Country:

You will be able to activate your card, once you receive it in the mail. Until your card arrives, please disregard automated e-mails urging you to complete card activation.

Please feel free to contact us if you have any additional questions.

Sincerely,

Fedor

And certainly, I did enter my correct mail address. Then today, August, a month after I receive the uTest MasterCard sent from Payoneer US by Airmail.

With a very clear instruction, I have just activated the card successfully. There is one important note in the letter: "Do not use unless funds are loaded. Some ATM will "eat" your card if you use without any fund available." of course :).

So that's it. Just share to my dear testing friends. Let's join this great cummunity of Tester Professionals. Hopefully after I activate the card I can get a project from uTest, kaka Happy Testing... :D

»»  read more

Agile Testing Webinar

Date: Tuesday, 23th September, 2008, Time: 11:00am EDT;
Vietnamese timezone: 10h PM same day;
Host: uTest.com

Agenda:
    * Agile testing overview
          o Agile terminology
          o Different Test Phases
    * The Tester role in the Agile process
    * Testing in short iterations
    * Deliver tested features/ Test Driven Development (TDD)
    * Testing and the end user

P/S: As part of our Agile Testing Webinar series, we will also be giving our participants a copy of our new Agile Testing Case Study.

>> Few months ago, I joined a Webinar at SQA Forum, it's so interesting. Now this Webinar topic is very practical to me. Since my QC team at Agile Mobile is practicing the test in Agile/Scrum process. This also very helpful for tester in general, you will have chance to practice this very soon because of the wide spread of Agile these days, *All* the world now use it. Why not? It's totaly 100% free. You need to use VoIP card to have the sound. Or you may try Gtalk to call that conference for free (never try before, just heard, will try this time :)

I have registered already, kaka. (see the last screen below). The uTest community is crowded (~7000), and the space for this Webinar is limited I'm sure. Then if you're really care about Agile Testing, so what are you waiting for Let's go to here for register. Come on guys, hurry up... time and tide wait for no man :)

Some Reference Link about Agile Testing: [to read before come to seminar]
1/ Agile Software Development in general at wiki
2/ Keys to Agile Testing Success (uTest blog)
3/ Agile Testing - Flexible Code, Flexible Testing - (uTest blog)  

4/ Using Scrum to Manage the Testing Effort (Bob Galen)
5/ Agile & Scrum: What are these methodologies and how will they impact QA/testing roles?(QA Zone)
6/ Agile Functional Test Automation (Worksoft Inc.)

(3 presentation above (4,5,6) are found thru the nights when I searching document for Agile Testing. Just listed here FYI my dear testers.)

-------------------------------------------
Update Sep-25-2008: Download the slide

Case study Second Rotation at uTest

»»  read more

Why Testing Is Necessary

+ As the question raised before at Part 1- Is QC Really Necessary? Here is the very long detail answer looking thru an PM's eyes, my ex-chief at Agile Mobile. But to me, it's just rather simple, it's a MUST not SHOULD, and I'm glad to see that many people these days are aware of this and it's still increasing. Actually, there are many answers you may found on the Internet. And we wouldn't say what is wrong, what is right. But right here, I would just like to point out an idea about this interesting question, here it is..

All know that we have many kinds of testing: functional, integration, performance, unit testing etc. Each type is done by some members, may be it is done by whom implement feature or someone else, may be it is executed by others. In software industry we have two terms Verification and Validation. Verification means build the right thing and validation is build the thing right. Mostly verification activities belong to functional testing and it needs someone takes user role to verify the product to see whether that product meets client’s expectation. It should not be done by developer himself but someone else (I avoid to use QC here, you will know the reason later). And I'm sure it will be better if the job done by the BA team or even the best situation that client involve deeply to project and validate whether team do right or wrong. But BA member is limited also requiring user involve deeply is a illusion, so we need to have third-party side can play the user role and now we have the team named QC. In fact, the major activities of QC team is making sure the quality of product meet client’s expectation not creating test cases, test procedures etc, which is only the tool help QC team to meet that goal. Moreover, we do not need QC think out-side what developers, BA can not think because it is not a requirement to QC team and it depends on each member’s capacity.

In part 1, developer had wrong argument on testing type, he thinks that unit test can cover integration and functional testing, it is incorrect of course. In general, we have only two types of defect related to developer team, they are:

1. Lack of unit test, they can not cover all cases of testing. In almost cases, I can say defects occur by Null Pointer or Wrong Format are lack of unit test.
2. Ambiguous requirement: they understand the requirement wrongly.

The developer’s responsibility must be making sure they perform unit test very well, it is not the major responsibility of QC is catch up defect for developers by lacking of unit test. The major role of QC team is verifying whether the developer understand requirements and implement it correctly. It does not mean the QC is expert than developer in requirements and system. If some defect is posted to DMS (Defect management system), it does not mean developer team do the wrong thing but it means the developer and “simulated” user (QC member) understand the system in different ways. Such defect may be correct and may be not, it depends on the argument between them with the involvement of BA and client if needed.

For each project, the difficulty of functional testing is different. If project is just a e-learning website, it is rather easy to play the end user role but if your project is a development framework the skill of QC sometimes require more than developer skill, especially if QC team is required using gray box testing. So, the thinking that QC member is un-skilled guys that is not un-fair and un-practiced assessment.

So my answer is we all need to have QC team in any projects but we should do understand their responsibility clearly, developer has his job and QC has her job and they are completely different. The skill-set for each roles are different too, so just be professional and support other sides during developing software is the good way instead to have the wrong perception to QC team.

(Source: my ex-chief blog)

»»  read more

Is QC Really Necessary ?

I think we got the answer already. I, as a QC, do not try to answer this question myself. But here, I would just like to refer to an interesting artical describing how a PM fell into this situation in a difficult meeting. This is from Hai Phuc Nguyen - My chief thought who was interview me and gave me the key to open AM door and I have learn a lot from him since then. He's very kind and done very good so far in his responsibility as a Product Manager at Agile Mobile. Now he is going start his private business, and will leave AM at the end of next week. Good luck to you Hai on the new venture and Big Success will come to you very soon :)

Actually, this entry was written last year on Feb-2007 but I'm sure it's still a wondering question these days in IT folks. Now let's see how difficult meeting is...

Once in a while, there was a meeting like this:
(recommend to whom is devloper or manager and read this, and QC too :))

"
Developer: hi manager, in my opinion we should discard our QC team because they do not add any value. All defects they found can be discovered by developer team, they repeat developer team activities that make the project’s cost is increased
Manager (looked so angry): what did you say? it is so funny when we discard QC team, who perform testing for us and who take responsibility of delivery’s quality?
Developer: you have emphasized we need to reduce the redundant cost, try to avoid duplicated activities, increase the productivity. I just base on your goals to propose that idea!
Manager: It’s ok. Just return my questions, can you provide more detail on your suggestion? - the manager does think developer’s suggestion is not the good one but he want to point out the mistakes of developers.
Developer: Let’s I raise my point. In our project, we have the following activities:
1. BA team collect and write requirements.
2. Developer and QC team review the requirements
3. Developer write the code, QC create the test case
4. Developer send build to QC for verify the build.
We can save the cost by developer team, why QC team need to test because all kind of tests can be covered by developer team.
Manager (looks patient): who will create test cases and execute test to be sure the product satisfy the requirements from client.
Developer: most of defects in tracker belong to lack of unit test from developer team, that we can cover by unit test and use coverage tool to identify what code is not tested by ourselves.
Manager: if you use unit test, you can not sure the quality of product because one developer is assigned to separated features and no one takes responsibility of functional testing.
Developer: Business Analysis - BA team can use some testing framework for functional testing, such frameworks are available for free like Fit framework.
Manager: how about the integration testing?
Developer: if you are sure unit run well and we manage the contract among modules well, integration takes less effort for testing. We can write the integration test by code and it is executed automatically.
Manager (becomes embarrassed): how about the performance?
Developer (laughs): we can do better, we log the main activities, analyzing data for whole process not just run the application and read the result.
Manager (not find appropriate words to criticize developer’s arguments): I have not seen this case before because all projects have QC team. Let’s have that team in our project. The meeting is closed. 
"

There are two items need to be clarified here:

1. What is the main responsibility of QC team? It is just cover defects cause by developer due to lack of unit test, if so we do not need to have QC team in case developers are guru and they write enough unit test to cover all implemented code?   (Sorry, I have some words on this, here)

2. Whether all activities of QC team can be done better by other team like BA, developer team. So do we need to have QC team for your project or we only keep a little effort for QC team.

What do you think about these two items and if you were manager in above story, what will you say to developer and persuade them maintain QC team is a must for project to meet product’s quality?

(Source: Hai's blog)

P/S: this is another same same interesting discussion from Buu Nguyen's blog.
>>> And if you are lazy to find the answer for yourself, go here for it

»»  read more

Relax giữa tuần with some funny msgbox

Đã complete thành công rồi mà còn error.

Gần đây ứng dụng mình đang test bắt đầu làm cuộc cách mạng msgbox. Làm mình chợt nhớ lại một cái link send long time ago about msgbox sent via Y!M. The link showed up many funny msgbox. Vốn thích sưu tầm, vậy là chỉ cần vài phút với Mr.G là có thể revise memory with this funny stuff related to testing zone.

Là một Tester bạn không thể không làm việc với các msgbox của các ứng dụng phần mềm, nếu không nói là 1 phần quan trọng trong UI Testing, vì đây là phần giao tiếp với user mỗi khi *đụng* chuyện. Đó cũng là nơi ứng dụng thể hiện mình *smart* or *stupid* :D. Là Tester bạn hoàn toàn nắm quyền sinh sát trong tay. Em nào lớ ngớ là trảm không nên thương tiếc.

Không biết các bạn Tester khác thế nào, riêng tôi khi test 1 ứng dụng nào là tôi lại thích sưu tầm những interesting error của ứng dụng đó, (thường dùng attach chung với bug report), và lẽ dĩ nhiên các msgbox luôn hiện diện trong bộ sưu tập ấy. Hiện nay, tôi vẫn còn lưu giữ trên máy tính của mình ko biết là bao nhiu (thousands :P) là picture of all kind of errors của các ứng dụng mà tôi đã và đang test. Còn sau đây là bộ sưu tập msgbox vui tôi sưu tầm và tập hợp lại từ internet. Just for fun. Enjoy it my dear testing friends. Hope u like it.

Dưới đây là một số hình trong bộ sưu tập 19 hình tôi sưu tầm được, all are funny i bet ;) For example:

Error ở đây là: NO ERROR :D

kêu người ta đóng ứng dụng mà ứng dụng nào đây, cái msgbox trống trơn :)

Báo lỗi mà lăng quăng kiểu này, user chỉ có pó chiếu :P

Xem tất cả 21 msgbox tại đây

Happy Testing hehe :)

(Nguồn: VnExpress và tùm lum)

»»  read more

Test Group Mission

the idea below extracted from this presentation

Have you ever wondered what is the mission of your testing team. I did and had some in my head. One day, I found this very short and fully list. I'd like to share with here for more discussion.


1. Find defects
2. Maximize bug count
3. Support a unit testing effort
4. Block premature product releases
5. Help managers make ship / no-ship decisions
6. Help stakeholders translate their requirements into acceptance tests
7. Minimize technical support costs
8. Conform to regulations
9. Minimize safety-related lawsuit risk
10. Assess conformance to specification
11. Find safe scenarios for use of the product (find ways to get it to work, in spite of the bugs)
12. Verify correctness of the product
13. Assess quality
14. Assure quality

To me, I feel little bit confused about (8) (9). Regard to number (3), it is not directly, but I think developers will have idea for themselves during test case review meeting. The rest was and is really my team mission :)

(Source: article here)

»»  read more

QAZone@Empirix is now combined with OTN

OTN stand for Oracle Technical Network. Yep, it's true. For now, if you click on the link qazone.empirix.com it will lead you to OTN. But now, the number of QA resource/document reduce a lot. They just keep some interview, that belong to QA zone before, and is the most favorite part of my visiting.

Last month, I had an entry about some interesting article of testing with some links direct to this resource, now it's not any more hic hic.. But fortunately, I downloaded some document there still with QAZone logo embed. You can download some of them here at my 4shared

Empirix is a provider of Voice and Web application testing and monitoring solutions. And let's take a look how Oracle found Empirix interesting to cooperate. That is e-Test suite.



To learn more about what the combination of Oracle and Empirix to bring benefit, just click here to download a PDF from OTN about this topic.

For now e-Test suite belong to Empirix who know after few years, it will be labeled with Oracle logo ?!?

And here is the link to OTN which contain sort of interview testing-celebrity about industry trend and QA/QC stuff. It's nice to visit and read them all. I paste here some articles I feel interesting and related to my job currently:

	How to Motivate Your QA Team (PDF) Keeping and motivating your team without increasing your budget
	Agile and Scrum From a QA Perspective (PDF) Agile & Scrum: What are these methodologies and how will they impact QA/testing roles
	Managing Up: Communicating the Value of Testing Throughout the Organization (PDF)
	When to Automate your Testing (and when not to) (PDF)
	OTN Interview with Bob Galen: Agile and Scrum Learn more about agile and Scrum development methodologies
	OTN Interview with Rex Black: Automation, ISTQB certification & Industry Trends Read about how the ISTQB certification works
	OTN Interview with the team behind uTest: How to get paid to find bugs uTEST is a community for testers looking for additional hand-on experience and supplemental income
	OTN Interview with Paul Gerrard: Risk-based Testing & Industry Trends Learn more about the testing industry in EMEA and worldwide trends
	OTN Interview with Jon Bach: Exploratory Testing Get to know Jon Bach better and learn about exploratory testing and session-based test management

»»  read more