<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:blogger='http://schemas.google.com/blogger/2008' xmlns:georss='http://www.georss.org/georss' xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-3503296498280484138</id><updated>2024-10-02T13:22:28.764-07:00</updated><category term="Live Deployment"/><category term="MSTB"/><category term="Penetration Tester"/><category term="QA procedure"/><category term="SOFTEC"/><category term="Security"/><category term="Software Tester"/><category term="TPI"/><category term="TPI-Next"/><category term="Test Design"/><category term="Test Plan"/><category term="Web Application"/><category term="food industry"/><category term="introduction"/><category term="marketing"/><category term="view"/><title type='text'>Software Testing and Quality Assurance</title><subtitle type='html'>Personal view from a Quality minded person for&lt;b&gt; Software Testing&lt;/b&gt;, &lt;b&gt;Software QA&lt;/b&gt;, &lt;b&gt;Web Testing&lt;/b&gt;, &lt;b&gt;Blackbox Testing&lt;/b&gt; and &lt;b&gt; Quality Assurance ISO9001:2000&lt;/b&gt; testing procedure.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://qasoftware-usability.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default?redirect=false'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>17</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-638641142742827442</id><published>2012-05-01T19:13:00.001-07:00</published><updated>2012-05-01T19:13:34.509-07:00</updated><title type='text'>Being a Software Tester</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
I am passionate with my role as a tester in Software Development. Being a software tester require me to always think out of the box, be creative and patient. &lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://qasoftware-usability.blogspot.com/feeds/638641142742827442/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3503296498280484138/638641142742827442' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/638641142742827442'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/638641142742827442'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2012/05/being-software-tester.html' title='Being a Software Tester'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-2650688716636347836</id><published>2012-05-01T18:59:00.000-07:00</published><updated>2012-05-01T18:59:02.001-07:00</updated><title type='text'>My views of Quality - QA Software</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;div&gt;
My skill, knowledge and experience in Food Quality management is very useful in Software Testing and QA. The basic principle of Quality is applicable to all type of industry. The difference is mainly in the Risk Factors Management and Implementations. Food is a perishable goods, it risks is mainly on how to extend the shelf-life of the foods while still maintaining it&#39;s freshness, retaining it&#39;s nutrients and keeping it free from biological, chemical and microbiological contamination. On the other hand, Software industry has different type of risks depending on it&#39;s purpose of usage. The risk is focusing more on it&#39;s features, functionality and accuracy. The example of high risk software is the one being used in hospitals such as life-support machinery and dialysis machine.&lt;br /&gt;
In food manufacturing, HACCP (Hazard Analysis Critical Control Point) is one of the compulsory preventive approach to be implemented. &lt;a href=&quot;http://www.rbcs-us.com/&quot; target=&quot;_blank&quot;&gt;Rex Black&lt;/a&gt; has shared a similar preventive approach to be implemented in software development, which is called &lt;a href=&quot;http://www.rbcs-us.com/images/documents/Critical-Testing-Processes.pdf&quot; target=&quot;_blank&quot;&gt;Critical Testing Process&lt;/a&gt;.&lt;br /&gt;
Quality and process improvement in manufacturing is very easy to be implemented and improved, however, it is very difficult and challenging in software industry.&lt;/div&gt;
&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/2650688716636347836'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/2650688716636347836'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2012/05/my-views-of-quality-qa-software.html' title='My views of Quality - QA Software'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-2785604547972335219</id><published>2012-03-16T09:47:00.003-07:00</published><updated>2012-03-16T09:47:29.671-07:00</updated><title type='text'>Learning Coded UI Test in Visual Studio 2010</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
I have researched on UI Automation feature that available in Visual Studio 2010 since last 3 weeks.&lt;br /&gt;
It was a very tough journey for me since it was my first experience of using Visual Studio and it&#39;s features.&lt;br /&gt;
My first approach was to have a complete environment of testing with VS2010. This means that I need to have Team Foundation Server (TFS) completes with Test Manager and VS2010 Ultimate. My first approach was to install them individually, which was very time consuming and challenging. Somehow I&#39;ve stumbled on &lt;a href=&quot;http://blogs.msdn.com/b/briankel/&quot; target=&quot;_blank&quot;&gt;Brian Kelle&lt;/a&gt;r blogs in MSDN whereby he has uploaded Virtual PC with complete VS2010 environment. That&#39;s make my life much easier apart from the long hour and large volumes of downloaded vpc.&lt;br /&gt;
I&#39;ve also downloaded many videos from YouTube on Coded UI Test and UI Automation testing. I&#39;ve watched the videos hundreds of hours so that I can get a better picture on the tool. I&#39;ve also practiced hands-on in the victual PC, trying to follow all the examples shown in the videos.&lt;br /&gt;
My big challenge in using Coded UI Test was in understanding it&#39;s framework and coding. A lots of guessing games here and there on the terms, the codes and it&#39;s features. Somehow, I&#39;ve manage to get around and get my full understanding on the tool.&lt;br /&gt;
New feature called Coded UI Test Editor is only available for MSDN subscribers in Feature Pack 2. This editor is very useful in editing the generated XML file for Coded UI Test.&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://qasoftware-usability.blogspot.com/feeds/2785604547972335219/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3503296498280484138/2785604547972335219' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/2785604547972335219'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/2785604547972335219'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2012/03/learning-coded-ui-test-in-visual-studio.html' title='Learning Coded UI Test in Visual Studio 2010'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-4879470493005960875</id><published>2010-07-24T06:40:00.000-07:00</published><updated>2010-07-25T17:51:27.842-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="TPI"/><category scheme="http://www.blogger.com/atom/ns#" term="TPI-Next"/><title type='text'>Improving Test Process based on TPI and TPI-Next</title><content type='html'>One of the topics presented in SOFTEC2010 is TPI and TPI-Next. TPI is stand for Test Process Improvement and TPI-Next is the evolution of the TPI. TPI-Next is also known as Business Driven Test Process Improvement (BDTPI) by some people as it is driven by business goal.&lt;br /&gt;
&lt;br /&gt;
The model is looks at test process from different points of view, which are called Key Areas. Examination of each Key Area leads to classification of the test process into certain Levels of maturity. Checkpoints are assigned to each Level to ensure that the classification into levels is done objectively. Lastly, Improvement suggestions were added to the model for suggesting on how to achieve a certain level.&lt;br /&gt;
&lt;br /&gt;
A better understanding of TPI model was achieved from attending the workshopduring SOFTEC2010. Lee Copeland has shared on TPI and Graham Bath shared on TPI-Next. Both of the trainers are very experienced and well-versed in applying TPI and TPI-Next with their clients worldwide.</content><link rel='replies' type='application/atom+xml' href='http://qasoftware-usability.blogspot.com/feeds/4879470493005960875/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3503296498280484138/4879470493005960875' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/4879470493005960875'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/4879470493005960875'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2010/07/improving-test-process-based-on-tpi-and.html' title='Improving Test Process based on TPI and TPI-Next'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-3942712896663768450</id><published>2010-07-21T08:15:00.000-07:00</published><updated>2010-07-25T17:52:26.637-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MSTB"/><category scheme="http://www.blogger.com/atom/ns#" term="SOFTEC"/><title type='text'>SOFTEC2010: Bridging the Gap (19 - 21 July 2010)</title><content type='html'>&lt;a href=&quot;http://www.facebook.com/pages/SOFTEC2010-Conference/&quot;&gt;&amp;nbsp;SOFTEC2010&lt;/a&gt; is an eye-opener for me. I&#39;ve heard about Software Testing Conference (SOFTEC) since 2008, it&#39;s first year being held in Malaysia, but only this year I&#39;m able to participate. For that, I&#39;m very grateful with my company for sponsoring my ticket and MSTB for given me another ticket for FREE so that I can bring one of my team member to the conference.&lt;br /&gt;
&lt;br /&gt;
There are 2 main objectives I&#39;ve planned to achieve from SOFTEC2010:&lt;br /&gt;
1) Process Improvement &lt;br /&gt;
2) Testing Techniques&lt;br /&gt;
&lt;br /&gt;
Yes, I&#39;m happy to say that I did achieved both of the objectives and most importantly, being there, listened to the experts and participate in the workshops &amp;amp; tutorials were highly valuable experience that can&#39;t be gained just&amp;nbsp; by reading. &lt;br /&gt;
&lt;br /&gt;
Among the speakers I liked most were Lee Copeland &amp;amp; Graham Bath, both sharing about TPI and TPI-Next, Rex Black on Risk-based Testing, Dave Miller on his experience in applying TDD in FedEx and Chris Rupp on Requirement Engineering.&lt;br /&gt;
&lt;br /&gt;
I can&#39;t wait for SOFTEC2011.... and expecting more goodies to come.&lt;br /&gt;
&lt;br /&gt;
MSTB has done great work in organizing Software Testing Conference 2010 (SOFTEC2010).</content><link rel='replies' type='application/atom+xml' href='http://qasoftware-usability.blogspot.com/feeds/3942712896663768450/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3503296498280484138/3942712896663768450' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/3942712896663768450'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/3942712896663768450'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2010/07/softec2010-bridging-gap-19-21-july-2010.html' title='SOFTEC2010: Bridging the Gap (19 - 21 July 2010)'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-1175505654389204201</id><published>2010-06-25T04:08:00.000-07:00</published><updated>2010-07-25T17:56:00.949-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Software Tester"/><title type='text'>Is anyone can be a Software Tester?</title><content type='html'>Yes and No, depending on many conditions, scenarios and the level of testing effort requires.&lt;br /&gt;
&lt;br /&gt;
If you want to hire a full-time Software Tester, you need to be very selective and stringent in the selection process. Their skills, knowledge and experiences must matched with your team needs to progress. Above all, is their personality and character, either the candidates able to integrate with your team and development team smoothly. For fresh grads, the main criteria will be their attitude and personality that we safely feel confident they can be mould to become a tester. &lt;br /&gt;
&lt;b&gt;&lt;br /&gt;
&lt;/b&gt;</content><link rel='replies' type='application/atom+xml' href='http://qasoftware-usability.blogspot.com/feeds/1175505654389204201/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3503296498280484138/1175505654389204201' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/1175505654389204201'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/1175505654389204201'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2010/06/is-anyone-can-be-software-tester.html' title='Is anyone can be a Software Tester?'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-8594188134268786632</id><published>2010-06-23T06:00:00.000-07:00</published><updated>2010-06-23T06:00:32.424-07:00</updated><title type='text'>Bug Tracking Tools</title><content type='html'>I&#39;ve experienced with quite a few Open Source tools for tracking purposes such as Eventum, Mantis and Bugzilla. All these tools is useful on it&#39;s own way, depending on what features you are looking at. I&#39;ve summarize below on the features for each tools.&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;https://launchpad.net/eventum/&quot;&gt;1.&amp;nbsp; Eventum&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Eventum is a user-friendly and flexible issue tracking system that can  be used by a support department to track incoming technical support  requests, or by a software development team to quickly organize tasks  and bugs. Eventum is used by the MySQL AB Technical Support team, and  has allowed us to dramatically improve our response times.&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://www.mantisbt.org/&quot;&gt;2. Mantis&lt;/a&gt;&lt;br /&gt;
Mantis is an easily deployable, web based bugtracker to aid product bug  tracking. It requires PHP, MySQL and a web server.&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://www.bugzilla.org/&quot;&gt;3. Bugzilla&lt;/a&gt;&lt;br /&gt;
Bugzilla is a &quot;Defect Tracking System&quot; or &quot;Bug-Tracking System&quot;. Defect  Tracking Systems allow individual or groups of developers to keep track  of outstanding bugs in their product effectively.</content><link rel='replies' type='application/atom+xml' href='http://qasoftware-usability.blogspot.com/feeds/8594188134268786632/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3503296498280484138/8594188134268786632' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/8594188134268786632'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/8594188134268786632'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2010/06/bug-tracking-tools.html' title='Bug Tracking Tools'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-6822065087597722508</id><published>2010-04-24T06:05:00.000-07:00</published><updated>2010-04-24T06:05:18.788-07:00</updated><title type='text'>New chapter in 2010</title><content type='html'>I started new year with new company, new position and new responsibilities...&lt;br /&gt;
&lt;br /&gt;
&amp;nbsp;Now I am a Software QA Manager for a Swedish-based company where the R&amp;amp;D department is only 2 years and I&#39;m the first Software QA. My first task is to get at least 1 Software Tester to handle on the existing project so that I can focus on the other important things.</content><link rel='replies' type='application/atom+xml' href='http://qasoftware-usability.blogspot.com/feeds/6822065087597722508/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3503296498280484138/6822065087597722508' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/6822065087597722508'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/6822065087597722508'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2010/04/new-chapter-in-2010.html' title='New chapter in 2010'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-3205981142994265208</id><published>2009-09-03T21:52:00.000-07:00</published><updated>2009-09-03T21:52:20.172-07:00</updated><title type='text'>How to be Creative in software testing?</title><content type='html'>As a professional QA, one must have a creative mind when testing any softwares. Being creative is achieved through experiences and&amp;nbsp;the appetite&amp;nbsp;to explore more.&lt;br /&gt;
For a starting point, QA need to&amp;nbsp;implant in their mind&amp;nbsp;that the software they are tested must be Configurable, Flexible and Maintainable in a long run.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/3205981142994265208'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/3205981142994265208'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2009/09/how-to-be-creative-in-software-testing.html' title='How to be Creative in software testing?'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-7465809917694378365</id><published>2009-09-01T22:25:00.000-07:00</published><updated>2009-09-01T22:35:54.853-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Penetration Tester"/><category scheme="http://www.blogger.com/atom/ns#" term="Security"/><category scheme="http://www.blogger.com/atom/ns#" term="Web Application"/><title type='text'>Web Application Security: The Beginner Story</title><content type='html'>With zero knowledge in Web Application Security, I have no choice but to choose Security as my Research Study. The starting point is very difficult and challenging. There are my terms I need to understand and know how it is work. Apart from the technical terms, I now can proudly say that I know the type of attacks &amp;amp; web vulnerability.&lt;br /&gt;Cross-site scripting, SQL Injection, Denial of Service and Access Control Management are some of the well-known security attacks.&lt;br /&gt;A &quot;white-hat hacker&quot; is normally called as Penetration Tester, in which they trying to attack the websites in order to assess it&#39;s security level.&lt;br /&gt;To be continue...</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/7465809917694378365'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/7465809917694378365'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2009/09/web-application-security-beginner-story.html' title='Web Application Security: The Beginner Story'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-1853309602601143981</id><published>2008-11-25T23:55:00.000-08:00</published><updated>2008-11-26T00:25:37.882-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Live Deployment"/><category scheme="http://www.blogger.com/atom/ns#" term="Test Design"/><title type='text'>BIG Deployment to LIVE!</title><content type='html'>Finally, the current Change Request is deployed to LIVE! What a relieve.&lt;br /&gt;Well, we have done the testing by phases and in different servers, i.e UAT, Training and Live servers. The type and quantity of testings is huge and repetitive just to ensure everything is working fine and as specified, without affecting the existing system behaviour.&lt;br /&gt;&lt;br /&gt;The things I&#39;ve learned from this Change Request:&lt;br /&gt;1. Testing by phases and at different servers is highly helpful for both QA and Developers.&lt;br /&gt;Reason: Practise makes perfect&lt;br /&gt;&lt;br /&gt;2. Need better Clarification and Understanding about the Change Request within the current system.&lt;br /&gt;Reason: Lots of hiccups are due to the lack of understanding in&lt;br /&gt;=&gt; the existing system behaviour&lt;br /&gt;=&gt; the Specifications &amp;amp; Requirements in the Change Request&lt;br /&gt;=&gt; the system design&lt;br /&gt;&lt;br /&gt;3. As for the QA, apart from what stated in #2, we also need to prepare the Test Design. The Test Design can only be 100% achieve if have better understanding of the above #2 criterias.&lt;br /&gt;&lt;br /&gt;4. Finally, I strongly disagree with the use of Test Cases when performing the testing. Test Cases is very time consuming and ineffective. I prefer to have a good Test Design, then from there prepare the Test List in simple way using simple method like table, matrix and forms.&lt;br /&gt;Reason: Faster, Simple, Easy &amp;amp; Usable - Everything in one place (Specs, Criterias &amp;amp; Test Results)&lt;br /&gt;&lt;br /&gt;All in all, testing is about one&#39;s passion. It&#39;s not everyday job for everybody. As it is a highly repetitive job, ones must have patient as well as highly imaginative in testing the same features but from different angles.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/1853309602601143981'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/1853309602601143981'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2008/11/big-deployment-to-live.html' title='BIG Deployment to LIVE!'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-8314314060241821975</id><published>2008-10-30T05:32:00.000-07:00</published><updated>2008-11-06T18:08:51.009-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="marketing"/><title type='text'>FREE Hosting Solution with Rich Niche Websites</title><content type='html'>I came accross &lt;a href=&quot;https://paydotcom.com/r/54737/process516/21250805/&quot;&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;this website&lt;/span&gt;&lt;/a&gt; when I was browsing about Software testing. The owner is still in final beta stage so they offer VERY VERY CHEAP price for public to try that is only $0.01 for every 30 days. In return, they get the feedback from a big group of users. Sounds impossible rite? Well, if you don&#39;t believe me just &lt;a href=&quot;https://paydotcom.com/r/54737/process516/21250805/&quot;&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;Click Here&lt;/span&gt;&lt;/a&gt; to view the offer, then you judge yourself.&lt;br /&gt;This are the goods offered by &lt;a href=&quot;https://paydotcom.com/r/54737/process516/21250805/&quot;&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;them&lt;/span&gt;&lt;/a&gt;:&lt;br /&gt;- Hosting solution to help users make content rich niche websites.&lt;br /&gt;- Automatic updating with new content makes google happy = free traffic = free customers.&lt;br /&gt;- Control advertising to profit from their passions.&lt;br /&gt;- Create passive income by gathering useful information.&lt;br /&gt;- Easy interface with no technical background needed.&lt;br /&gt;- Loaded with affiliate products ready to plug in to their web site.&lt;br /&gt;- Hosting of users own domains.&lt;br /&gt;- Low cost management, affiliate, design and hosting solution – all in one.&lt;br /&gt;- Imagine a user having 20-30 niche sites generating on average a $5 profit per day. This gives the user a nice addition to their regular income. All automated after it has been setup.&lt;br /&gt;Wanna know more please go to here: &lt;a href=&quot;https://paydotcom.com/r/54737/process516/21250805/&quot;&gt;&lt;span style=&quot;font-size:180%;&quot;&gt;$0.01 Website&lt;/span&gt;&lt;/a&gt;&lt;br /&gt;&lt;span style=&quot;font-size:78%;&quot;&gt; (Note: By the way, the offer is only for October 2008. After that it&#39;s chargeable which Standard $17/month)&lt;/span&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/8314314060241821975'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/8314314060241821975'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2008/10/free.html' title='FREE Hosting Solution with Rich Niche Websites'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-3723365773323260299</id><published>2008-10-13T15:00:00.000-07:00</published><updated>2008-11-06T18:10:47.257-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="view"/><title type='text'>Why I am a Software QA?</title><content type='html'>Being a Software QA is never been planned in my career prospects. It&#39;s all happen through lucks (I believe it&#39;s a Miracle), hardwork, preseverence and deep passion on what I&#39;m doing. People still keep on asking me why I become QA Software, which is totally out from my speciallity. My answer is very simple and easy, &quot;I am passionate about Quality. The core principles and objectives of Quality is applicable to all system, industry, organizations, or whatever you call it. The main things is we understand the main meaning of Quality.&quot;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/3723365773323260299'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/3723365773323260299'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2008/10/why-i-am-software-qa.html' title='Why I am a Software QA?'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-839768916695860502</id><published>2008-09-06T08:43:00.000-07:00</published><updated>2008-11-06T18:10:01.700-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="QA procedure"/><title type='text'>Black Box Testing</title><content type='html'>Black Box Testing is testing without knowledge of the internal workings of the item being tested. For example, when black box testing is applied to software engineering, the tester would only know the &quot;legal&quot; inputs and what the expected outputs should be, but not how the program actually arrives at those outputs. It is because of this that black box testing can be considered testing with respect to the specifications, no other knowledge of the program is necessary. For this reason, the tester and the programmer can be independent of one another, avoiding programmer bias toward his own work. For this testing, test groups are often used, &quot;Test groups are sometimes called professional idiots...people who are good at designing incorrect data.&quot; &lt;a href=&quot;http://www.cse.fau.edu/~maria/COURSES/CEN4010-SE/C13/black2.html&quot;&gt;1&lt;/a&gt; Also, do to the nature of black box testing, the test planning can begin as soon as the specifications are written. The opposite of this would be &lt;a href=&quot;http://www.cse.fau.edu/~maria/COURSES/CEN4010-SE/C13/glass.htm&quot;&gt;glass box testing&lt;/a&gt;, where test data are derived from direct examination of the code to be tested. For glass box testing, the test cases cannot be determined until the code has actually been written. Both of these testing techniques have advantages and disadvantages, but when combined, they help to ensure thorough testing of the product.&lt;br /&gt;&lt;br /&gt;Source taken from: &lt;a href=&quot;http://www.cse.fau.edu/~maria/COURSES/CEN4010-SE/C13/black.html&quot;&gt;http://www.cse.fau.edu/~maria/COURSES/CEN4010-SE/C13/black.html&lt;/a&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/839768916695860502'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/839768916695860502'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2008/09/black-box-testing-is-testing-without.html' title='Black Box Testing'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-8824121517218322025</id><published>2008-08-29T23:02:00.000-07:00</published><updated>2008-11-06T18:04:41.859-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Test Plan"/><title type='text'>Test management and bug tracking tools</title><content type='html'>As part of my responsibilities as SQA Engineer to upgrade our QA overall processes, I have to evaluate free tools for handling &lt;strong&gt;Test Management and Bug tracking&lt;/strong&gt;. Currently, my company has been using &lt;strong&gt;&lt;a href=&quot;http://eventum.mysql.org/wiki/index.php/Main_Page&quot;&gt;Eventum&lt;/a&gt;&lt;/strong&gt; for handling support issues as well as Project Releases for many years.&lt;br /&gt;We found that Eventum have limited features and capabilities which affects our efficiency and effectiveness in handling issues arise from Code Review and Software Testing. Furthermore, I can&#39;t find any free tools that can easily integrate with &lt;strong&gt;Eventum&lt;/strong&gt; for Test Project Managements. This lead us to source for new free tools that cater for both Test Project and Bug Tracking Managements.&lt;br /&gt;My new team member has suggested &lt;strong&gt;&lt;a href=&quot;http://www.mantisbt.org/&quot;&gt;Mantis&lt;/a&gt; &lt;/strong&gt;as he did used Mantis as the Bug Tracking tool in his previous company. My Manager also did used Mantis in her previous company. We evaluate Mantis as well as BugNet and few more bug tracking tools. Finally, we have decided to use Mantis as it is quite similar with Eventum but with additional features, capabilities and catered for multi-level projects. At the same time, we also look for Test Project Management tool that can easily be integrated with Mantis. &lt;strong&gt;&lt;a href=&quot;http://www.teamst.org/&quot;&gt;TestLink&lt;/a&gt;&lt;/strong&gt; is the best choice so far.&lt;br /&gt;With &lt;strong&gt;TestLink&lt;/strong&gt;, we can create the&lt;strong&gt; Test Cases&lt;/strong&gt; for the &lt;strong&gt;Test Project&lt;/strong&gt; dynamically and collectively. The testing is only be executed after created a &lt;strong&gt;Test Plan&lt;/strong&gt; for the &lt;strong&gt;Test Project&lt;/strong&gt;. Meaning that, each Test Project can have many Test Plan, which we previously called it as Releases in the Eventum. Once the Test Plan is created, the Test Cases is pooled from the &lt;strong&gt;Test Specification&lt;/strong&gt; and assigned to the &lt;strong&gt;Tester&lt;/strong&gt;. The assigned Tester will execute the Test Cases and manually select the option for the test outcome, which is either Failed, Blocked or Passed. For Failed or Blocked outcomes, we need to click on the bug&#39;s icon to enter the Mantis&#39;s Issue ID. We have customized this part where when the Tester click on the icon, they will automatically pointed to Mantis and able to report the issue, without need to login at different page. The same goes to Mantis where we have added link at each issue for the specific Test Case. Meaning that the &lt;strong&gt;QA/Tester&lt;/strong&gt; focal point is the TestLink, while the Developer is Mantis.&lt;br /&gt;As I&#39;ve use both TestLink and Mantis now for few projects, I am very happy to say that both tools has complemented each other very well and most importantly has improve our efficiency and effectiveness tremendously.</content><link rel='replies' type='application/atom+xml' href='http://qasoftware-usability.blogspot.com/feeds/8824121517218322025/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3503296498280484138/8824121517218322025' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/8824121517218322025'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/8824121517218322025'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2008/08/test-management-and-bug-tracking-tools.html' title='Test management and bug tracking tools'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-6457971037616232798</id><published>2008-08-29T21:00:00.000-07:00</published><updated>2008-11-06T18:07:33.312-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="food industry"/><title type='text'>My views of Quality - Food Industry</title><content type='html'>I&#39;m graduated from &lt;a href=&quot;http://www.unsw.edu.au/&quot;&gt;The University of New South Wales, Australia &lt;/a&gt;in Bachelor of Science and majored in Food Science and Technology. I was really enjoyed my university years and looked forward to become a professional in Food related sectors. My most favorite subject was called Quality Evaluation and Control. Here I&#39;ve learned the basic concepts of what the real meaning of Quality, such as Quality Assurance, Quality Control, Quality Management, &lt;a href=&quot;http://www.iso.org/&quot;&gt;ISO9001:2000 &lt;/a&gt;etc and how to apply the concepts for different type of risks. At that point, I&#39;ve already set my mind to pursue my career in Food Quality Management.&lt;br /&gt;Little did I wonder that in Food Industry, Quality is the most critical issues to handle. The risk is so high that require us to be innovative, creative and knowledgeable but at the same time to be firm in decision-making. Quality is about end-to-end process which started with the raw materials and only ends at the consumption point, without ignoring any single point of contacts that might be critical for the process. Therefore, HACCP become the most applicable and sought after certification in Food Industry. &lt;a href=&quot;http://www.foodsafety.gov/~lrd/haccp.html&quot;&gt;HACCP&lt;/a&gt; is stand for Hazard Analysis Critical Control Points, that analyzing the end-to-end process to determine the critical points of the process that will affects the overall quality. Once the critical points determined, it was analyzed for the risk levels and necessary measures to be taken. Therefore, the risk is properly handled, managed and controlled throughout the process, from preparing raw materials to the point of consumption.&lt;br /&gt;Take for example, an ice cream manufacturing company. First of all, they have to make sure that the raw materials they ordered is as per specifications and not expired. Raw materials is checked against the required specification. Once the raw materials meet the specifications, they have to make sure that the equipments is cleaned and in good working conditions. The production environment must be clean, safe and free from contaminations. Then, the production process must be followed and monitored closely, from mixing, packing to hardening and so on. Transporting ice cream from factory to the customers is also need to be considered. Then, the storage of the ice cream at the customer sites must also taken into consideration up to the point of consumption. The quality is maintained and controlled throughout the food chains at the determined critical points. Missing or ignore one of the critical points might affetcs the quality of the ice cream directly and indirectly.&lt;br /&gt;Now, I am working as Software QA Engineer. Though in Software Quality we don&#39;t apply HACCP principles, the concept is still applicable where Quality is starting from the beginning of the project until delivered. We use different in Software Quality as the risk management is different.</content><link rel='replies' type='application/atom+xml' href='http://qasoftware-usability.blogspot.com/feeds/6457971037616232798/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3503296498280484138/6457971037616232798' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/6457971037616232798'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/6457971037616232798'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2008/08/my-views-of-quality-food-industry.html' title='My views of Quality - Food Industry'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3503296498280484138.post-6209287020107313999</id><published>2008-08-29T15:52:00.001-07:00</published><updated>2008-11-06T18:07:10.654-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="introduction"/><title type='text'>My Life before become QA Software Engineer</title><content type='html'>My previous company simply assigned me as QA and Operational Executive. I was responsible for the overall quality of the management of the Company as well as Production and Software development since I am the only QA there. I have developed an ISO9001:2000 Quality Management for the Company. Apart from that, I have developed SOP for the Production department, handled the Customer complaints, managed the Production Network &amp;amp; databases, as well as managed Software Testing and deployments. The hectic work schedule without having someone to assisst my work has taught me to be multi-tasker, efficient and be more pro-active. I&#39;ve quickly learned the art and skill of good software tester. All-in-all, I have gained an invaluable experience throughout my 2.5 years there. Now I know what I want to become and vision myself as Professional Software QA.</content><link rel='replies' type='application/atom+xml' href='http://qasoftware-usability.blogspot.com/feeds/6209287020107313999/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3503296498280484138/6209287020107313999' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/6209287020107313999'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3503296498280484138/posts/default/6209287020107313999'/><link rel='alternate' type='text/html' href='http://qasoftware-usability.blogspot.com/2008/08/my-life-before-become-qa-software.html' title='My Life before become QA Software Engineer'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>