Here are some of the topics covered in this book:

• Fundamentals of software testing
• When defects gets introduced in SDLC?
• Why does software have defects?
• What is Verification?
• What is Validation?
• Software Testing Techniques
• Static Testing
• White Box Testing
• Black Box Testing
• Gray Box Testing
• Objectives of Testing
• Software testing Principles
• Reviews
• Types of Reviews
• UI / GUI Testing
• Test Planning
• Test Plan and Test Plan Template
• SRS/FRS template
• Test Scenario
• Example Test Scenarios
• Test Case
• What is a good test case?
• Test case design techniques
• Requirement traceability Matrix (RTM)
• Defect Reporting
• Configuration Management
• Software Configuration Tools

**************************

If you want to stay updated with latest information from software testing industry and more testing free eBooks, please consider signing up for our free newsletter by providing your email address in below sign up form:

Download this eBook:
Just right click on below link and then click on “Save link as” to save this eBook zip file on your computer:

==>> Manual Testing Help eBook Download

If you enjoy this eBook don’t forget to share it with your friends. You can also put all your queries in comments below.

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
Manual Testing Help eBook – Free Download Inside!

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

As a tester, you have to test the ‘Examination Results’ module of the website of a university. Consider the whole application has been integrated and it is in ‘Ready for Testing’ state. ‘Examination Module’ is linked with ‘Registration’, ‘Courses’ and ‘Finance’ modules. Assume that you have adequate information of the application and you created a comprehensive list of test scenarios. Now you have to design, document and execute these test cases. In ‘Actions/Steps’ section of the test cases, you must mention the acceptable data as input for the test. The data mentioned in test cases must be selected properly. The accuracy of ‘Actual Results’ column of TC Document is primarily dependent upon the test data. So, step to prepare the input test data is significantly important. Thus, here is my rundown on ”DB Testing – Test Data Preparation Strategies”.

Properties of Test Data:

The test data should be selected precisely and it must possess the following four qualities:

1. Realistic: By realistic, it means the data should be accurate in the context of real life e.g. in order to test ‘Age’ field, all the values should be positive and 18 or above. It is quite obvious that the candidates for an admission in the university are usually 18 years old (this might be defined in requirements).

2. Practically valid: This is similar to realistic but not the same. This property is more related to the business logic of AUT e.g. value 60 is realistic in age field but practically invalid for a candidate of Graduation or even Masters Programs. In this case, a valid range would be 18-25 years (this might be defined in requirements).

3. Versatile to cover scenarios: There may be several subsequent conditions in a single scenario, so choose the data shrewdly to cover maximum aspects of a single scenario with minimum set of data, e.g. while creating test data for result module, do not only consider the case of regular students who are smoothly completing their program. Give attention to the students who are repeating the same course and belong to different semesters or even different programs. The data set may look like this:

There might be several other interesting and tricky sub-conditions. E.g. the limitation of years to complete a degree program, passing a prerequisite course for registering a course, maximum no. of courses a student may enroll in a single semester etc. etc. Make sure to cover all these scenarios wisely with finite set of data.

4. Exceptional data (if applicable/required): There may be certain exceptional scenarios that are less frequent but demand high importance when occur, e.g. disabled students related issues.

Test data preparation techniques:

We have briefly discussed the important properties of test data and it also elaborates how test data selection is important while database testing. Now let’s discuss the ‘techniques to prepare test data’.

There are only two ways to prepare test data:

Method 1. Insert New Data:

Get a clean DB and insert all the data as specified in your test cases. Once, all your required and desired data has been entered, start executing your test cases and fill ‘Pass/Fail’ columns by comparing the ‘Actual Output’ with ‘Expected Output’.  Sounds simple, right? But wait, it’s not that simple.

Few essential and critical concerns are as follows:

1. Empty instance of database may not be available
2. Inserted test data may be insufficient for testing some cases like performance and load testing.
3. Inserting the required test data into blank DB is not an easy job due to the database table dependencies. Because of this inevitable restriction, data insertion can become difficult task for tester.
4. Insertion of limited test data (just according to the test cases needs) may hide some issues that could be found only with the large data set.
5. For data insertion, complex queries and/or procedures may be required, and for this sufficient assistance or help from the DB developer(s) would be necessary.

Above mentioned five issues are the most important and the most obvious drawbacks of this technique for test data preparation. But if there are some advantages as well:

1. Execution of TCs becomes more efficient as the DB has the required data only.
2. Bugs isolation requires no time as only the data specified in test cases present in the DB.
3. Less time required for testing and results comparison.
4. Clutter-free test process

Method 2. Choose sample data subset from actual DB data:

This is the feasible and more practical technique for test data preparation. However it requires sound technical skills and demands detailed knowledge of DB Schema and SQL. In this method you need to copy and use production data by replacing some field values by dummy values. This is the best data subset for your testing as it represents the production data.  But this may not be feasible all the time due to data security and privacy issues.

This strategy deserves one separate post which we’ll discuss in next article ‘Database gray-box testing’ and precautions to take while testing database.

This is a guest article by Rizwan Jafri.
Author is having more than 4 years of experience and Currently working as a Sr. QA Engineer in Systems Limited Lahore, Pakistan.

If you have any questions, please feel free to ask in below comment section.

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
Database Testing – Properties of a Good Test Data and Test Data Preparation Techniques

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

This is in fact most crucial test for time critical applications such as stock management systems which gets refreshed every minute creating huge load on web site as there are thousands of users accessing the web site at the same moment.

For such applications stress testing with more than 10,000 users is a basic test. The WAPT Pro comes with default “Load Agents” functionality to test average load on any web site. But for high capacity test with more than 10,000 users we can now leverage the power of x64 Load Engine extension.

x64 Load Engine is similar to Load Agents feature on WAPT Pro installation. The main difference is in the ability of load engine to generate huge load using 64 bit Windows systems. Using one 64 bit server you can dramatically increase the load testing capacity on web site under test. The x64 Load Engine can be configured in such a way that using slightly high end hardware you can easily generate more than 100k virtual users load on web site.

Assume that you want to stress test your web site with 100,000 concurrent virtual users. You can achieve this using 4 servers each with 25,000 virtual users. Setup this load engine on 4 systems and use them concurrently to achieve desired web site load. This powerful x64 Load Engine effectively utilizes the available memory resources on 64 bit system architecture.

WAPT Pro x64 Load Engine Installation:
- You can install x64 Load Engine on 64 bit version of Windows XP/2003/Vista/2008/Win7 OS.
- x64 Load engine works best on following hardware configuration:
Core i5/Phenom or CPU better than this, 8+ GB RAM and Gigabit Ethernet

How to install:    
x64 Load Engine is a WAPT Pro extension so it runs on WAPT Pro tool similar to Load Agents. To use this load engine you must have WAPT Pro installed first. You can download and install x64 Load Engine from below mentioned link. After installation you can start using load engine using the WAPT pro workplace itself.
Download WAPT Pro x64 Engine.

x64 Load Engine Pros:
- You can generate almost unlimited virtual users (test load) on Windows 64 system.
- Easy to install, learn and configure
Check out below screenshot to know the simplicity of x64 Load Engine Manager:

- No restrictions on the size of used virtual memory

x64 Load Engine Cons:
- No evaluation period available
- Works with WAPT Pro only

As said earlier in my comment, this tool is very useful for performance, stress & load testers. Other testers can get a glimpse of the performance testing scope which is very interesting to work on!

Please ask your queries in below comment section. Your feedback is always appreciated!

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
Want to Stress Test Website with 10,000+ Users? Use WAPT Pro x64 Load Engine

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

To celebrate this achievement I’m giving away a software testing book and one best book of the year (see details below). This giveaway will be open for a week starting from today 20th Nov 2011.

Check out what we are giving away:
1) QuickTest Professional Unplugged: 2nd Edition

2) Steve Jobs: The Exclusive Biography

Simple one rule to be the lucky winners!
Just add SoftwareTestingHelp.com to your Google+ circle. Similar to Facebook fan page now Google has rolled out Google+ pages and I have created brand new Google+ page for SoftwareTestingHelp where you will quickly get latest software testing updates and resources to download.

Click below Google+ badge to add us in your circle!
(Click on the badge, sign on to gmail and click on ‘Add to circle’ button in top right)

Two lucky winners who will add us on Google+ circle will be chosen randomly. Then I’ll announce the winners on Monday, Nov 28th on our Facebook fan page, Google+ page as well as on this blog post. Prizes will be shipped to winner’s addresses.

Thank you once again for all of your support. Good luck!

Update:
Winners are declared on our Google+ page: Software Testing Help on Google+

Thank you to all those who added us in their Google+ circle. If you have not added us in your Google+ circle yet, you should do it right away to get regular updates on testing articles, free ebooks and many more testing tips!!

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
Software Testing Book Giveaway – Celebrating 10000 Facebook Fans!!

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

How loadUI works:

LoadUI consist of building blocks called Components that you drag from the Component Toolbar to the Project you’re working on. These components connect to each other by wires and there is no limit for how many components that you can create and connect.

This way of drag-and-drop testing is especially useful during the test, since you can do complex load tests. The overview that you get makes it easier to try different combinations during the actual test and react to them immediately. In loadUI, Instant feedback is king.

Creating load tests in loadUI:

In order to run a test in loadUI you need at least two components (and an empty Project to work in);

- A generator
Which creates load, for example 100 requests per second.
- A Runner
That runs a certain type of test, for example a web test.

So let’s do it; drag out a Fixed Rate Generator and a Web Page Runner.
You can’t run them yet though first you need to connect them. You do this by connecting the nodes, or terminals, located above and below the components to each other with connections.

So now connect the Fixed Rate Generator to the Web Page Runner.

Now that everything is connected you should enter what website you want to load test into the Web Page Runner. Your test is now ready to run! Click the play button in the top menu to make your generator start sending requests to your site.

You can now follow, in real-time, how the test is going by clicking the Results Workbench button. Once there, double click on your Current Run and, from the left hand menu, drag out Response Time to the rack.

Congratulations! You have now created your first load test in loadUI. Play around with the widgets you have on your dashboard, experiment by adding some more, and try tracking other values in the Results Workbench. A good next step would to add an Assertion component and connecting it to the Web Page Runner. Then you can, for example, test how many times you your requests come through while following certain rules you set up (like taking less than 10 milliseconds).

Pro Tips:

Let a manager test!
This is the modern way of gorilla testing.  Let someone less proficient do the testing for you and see what breaks your service. It will also create an understanding and passion for testing within the management. A usual comment is “This is fun! But hard…”

It’s interactive, use it!
LoadUI is highly interactive and configurable in real-time, so take advantage of that.

Create a second test in real time against the same server with a different Generator and see if the system shows weaknesses when exposes to chaotic, life-like, behavior. Change this in real time and experiment.

Record your tests
Since loadUI is so interactive, reproducing the tests can be difficult. Use a screen recorder like Wink (which is free) to be able to replay your tests and see what caused the service to crash.

Work structured
LoadUI has support for test cases. Break up your tests into smaller test cases; you can always start them all at once.

Don’t double-work
If you have created functional tests in soapUI, you can simply run these in loadUI with the soapUI component. This way you don’t have to redefine the test another time in loadUI.

Write your own component
LoadUI is not only free; it’s open-source, too. That means that you can write your own components, in Groovy, if you wish. Only you set the limits for what is possible in LoadUI! Read more about creating your own components here.

Read more about loadUI, and download it here: Latest loadUI version

**********************************
This is a guest article by Henrik Olsson.
About Author:
Henrik is a software developer for loadUI from Stockholm, Sweden with an academic background in Distributed Systems and a passion for usability. He is experienced in teaching and thinks that most things can be easily explained, if well modeled and accurately targeted.

Editor’s Note:
I’m glad to share this open source load testing tool with my readers. LoadUI and soapUI are the best open source software testing tools from trusted company eviware (now SmartBear). If you are thinking to introduce load testing tool on your project try loadUI and soapUI (functional testing tool).  Also I personally used soapUI  for many projects and will soon cover it in a separate article. I love the power and beauty of these open source tools!

If you used this tool and have some tips to share, please do it in below comment section. Also we would be happy to hear and answer your queries on loadUI.

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
Load Testing Using loadUI – A Free and Open Source Load Testing Tool

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

“If QA (Quality Assurance) is done then why do we need to perform QC (Quality Control)?”, this thought may come to our mind some times and looks a valid point too.  This means if we have followed all the pre-defined processes, policies and standards correctly and completely then why do we need to perform a round of QC?

In my opinion QC is required after QA is done. While in ‘QA’ we define the processes, policies, strategies, establish standards, developing checklists etc. to be used and followed through out the life cycle of a project. And while in QC we follow all those defined processes, standards and policies to make sure that the project has been developed with high quality and at least meets customer’s expectations.

QA does not assure quality, rather it creates and ensures the processes are being followed to assure quality. QC does not control quality, rather it measures quality. QC measurement results can be utilized to correct/modify QA processes which can be successfully implemented in new projects as well.

Quality control activities are focused on the deliverable itself. Quality assurance activities are focused on the processes used to create the deliverable. QA and QC are both powerful techniques which can be used to ensure that the deliverables meet high quality expectations of customers.

E.g.: we have to use an Issue tracking system to log the bugs during testing a web application. QA would include defining the standard for adding a bug and what all details should be there in a bug, like summary of the issue, where it is observed, steps to reproduce the bugs, screenshots etc. This is a process to create deliverable ‘bug–report’. When a bug is actually added in issue tracking system based on these standards then that bug report is our deliverable.

Now, suppose some time at later stage of project we realize that adding ‘probable root cause’ to the bug based on tester’s analysis would provide some more insight to the Dev team, then we will update our pre-defined process and finally it will be reflected in our bug reports as well. This is how QC gives inputs to QA to further improve the QA.

Following is an example of a real life scenario for QA / QC:

QA Example:

Suppose our team has to work on completely new technology for upcoming project. Our team members are new to the technology. So for that we need to create a plan for training the team members in the new technology. Based on our knowledge we need to collect pre-requisites like understanding documents, design of the product along with the documents etc. and share with the team, which would be helpful while working on the new technology and even would be useful for any new comer in the team. This is QA.

QC Example:

Once the training is done how we can make sure that the training was successfully done for all the team members? For this purpose we will have to collect statistics e.g. number of marks the trainees got in each subject and minimum number of marks expected after completing the training. Also we can make sure that everybody has taken training in full by verifying the attendance record of candidates. If the number of marks of candidates are up to the expectations of the trainer/evaluators then we can say that the training is successful otherwise we will have to improve our process in order to deliver high quality training.

Hope this explains the difference between QA and QC.

****************
About Author: Meenal is Team Lead specialized in overall QA process for performing functional, data testing, performance testing and security testing for various projects. She is also worked on Waterfall and Agile models.

I would like all of you to please join this discussion and add more valuable points to it. Thanks.

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
Does Quality Assurance Remove Need for Quality Control?

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

Software industry has achieved a solid recognition in this age. In the recent decade, however, cyber-world seems to be even more dominating and driving force which is shaping up the new forms of almost every business. Web based ERP systems used today are the best evidence that IT has revolutionized our beloved global village.

These days, websites are not meant only for publicity or marketing but these have been evolved into the stronger tools to cater complete business needs. Web based Payroll systems, Shopping Malls, Banking, Stock Trade application are not only being used by organizations but are also being sold as products today.

This means that online applications have gained the trust of customers and users regarding their vital feature named as SECURITY. No doubt, the security factor is of primary value for desktop applications too. However, when we talk about web, importance of security increases exponentially. If an online system cannot protect the transaction data, no one will ever think of using it. Security is neither a word in search of its definition yet, nor is it a subtle concept. However, I would like to list some complements of security.

Examples of security flaws in an application:

1) A Student Management System is insecure if ‘Admission’ branch can edit the data of ‘Exam’ branch
2) An ERP system is not secure if DEO (data entry operator) can generate ‘Reports’
3) An online Shopping Mall has no security if customer’s Credit Card Detail is not encrypted
4) A custom software possess inadequate security if an SQL query retrieves actual passwords of its users

Security Testing Definition:
Now, I present you a simplest definition of Security in my own words. “Security means that authorized access is granted to protected data and unauthorized access is restricted”. So, it has two major aspects; first is protection of data and second one is access to that data. Moreover, whether the application is desktop or web based, security revolves around the two aforementioned aspects. Let us have an overview of security aspects for both desktop and web based software applications.

Desktop and Web Security Testing:
A desktop application should be secure not only regarding its access but also with respect to organization and storage of its data. Similarly, a web application demands even more security with respect to its access, along with data protection. Web developer should make the application immune to SQL Injections, Brute Force Attacks and XSS (cross site scripting). Similarly, if the web application facilitates remote access points then these must be secure too. Moreover, keep in mind that Brute Force Attack is not only related to web applications, desktop software is also vulnerable to this.

I hope this foreword is enough and now let me come to the point. Kindly accept my apology if you so far thought that you are reading about the subject of this article. Though I have briefly explained software Security and its major concerns, but my topic is ‘Security Testing’. In order to know further details of security aspects, kindly refer to – Web application security testing article.

I will now explain how the features of security are implemented in software application and how should these be tested. My focus will be on Whats and Hows of security testing, not of security.

Security Testing Techniques:

1) Access to Application:

Whether it is a desktop application of website, access security is implemented by ‘Roles and Rights Management’. It is often done implicitly while covering functionality, e.g.in a Hospital Management System a receptionist is least concerned about the laboratory tests as his job is to just register the patients and schedule their appointments with doctors. So, all the menus, forms and screen related to lab tests will not be available to the Role of ‘Receptionist’. Hence, the proper implementation of roles and rights will guarantee the security of access.

How to Test: In order to test this, thorough testing of all roles and rights should be performed. Tester should create several user accounts with different as well multiple roles. Then he should use the application with the help of these accounts and should verify that every role has access to its own modules, screens, forms and menus only. If tester finds any conflict, he should log a security issue with complete confidence.

2. Data Protection:

There are further three aspects of data security. First one is that a user can view or utilize only the data which he is supposed to use. This is also ensured by roles and rights e.g. a TSR (telesales representative) of a company can view the data of available stock, but cannot see how much raw material was purchased for production.

So, testing of this aspect is already explained above. The second aspect of data protection is related to how that data is stored in the DB. All the sensitive data must be encrypted to make it secure. Encryption should be strong especially for sensitive data like passwords of user accounts, credit card numbers or other business critical information. Third and last aspect is extension of this second aspect. Proper security measures must be adopted when flow of sensitive or business critical data occurs. Whether this data floats between different modules of same application, or is transmitted to different applications it must be encrypted to make it safe.

How to Test Data Protection: The tester should query the database for ‘passwords’ of user account, billing information of clients, other business critical and sensitive data and should verify that all such data is saved in encrypted form in the DB. Similarly (s)he must verify that between different forms or screens, data is transmitted after proper encryption. Moreover, tester should ensure that the encrypted data is properly decrypted at the destination. Special attention should be paid on different ‘submit’ actions. The tester must verify that when the information is being transmitted between client and server, it is not displayed in the address bar of web browser in understandable format. If any of these verifications fail, the application definitely has security flaw.

3. Brute-Force Attack:

Brute Force Attack is mostly done by some software tools. The concept is that using a valid user ID, software attempts to guess the associated password by trying to login again and again. A simple example of security against such attack is account suspension for a short period of time as all the mailing applications like ‘Yahoo’ and ‘Hotmail’ do. If, a specific number of consecutive attempts (mostly 3) fail to login successfully, then that account is blocked for some time (30 minutes to 24 hrs).

How to test Brute-Force Attack: The tester must verify that some mechanism of account suspension is available and is working accurately. (S)He must attempt to login with invalid user IDs and Passwords alternatively to make sure that software application blocks the accounts that continuously attempt login with invalid information. If the application is doing so, it is secure against brute-force attack. Otherwise, this security vulnerability must be reported by the tester.

The above three security aspects should be taken into account for both web and desktop applications while, the following points are related with web based applications only.

4. SQL Injection and XSS (cross site scripting):

Conceptually speaking, the theme of both these hacking attempts is similar, so these are discussed together. In this approach, malicious script is used by the hackers in order to manipulate a website. There are several ways to immune against such attempts. For all input fields of the website, field lengths should be defined small enough to restrict input of any script e.g. Last Name should have field length 30 instead of 255. There may be some input fields where large data input is necessary, for such fields proper validation of input should be performed prior to saving that data in the application. Moreover, in such fields any html tags or script tag input must be prohibited. In order to provoke XSS attacks, the application should discard script redirects from unknown or untrusted applications.

How to test SQL Injection and XSS: Tester must ensure that maximum lengths of all input fields are defined and implemented. (S)He should also ensure that defined length of input fields does not accommodate any script input as well as tag input. Both these can be easily tested e.g. if 20 is the maximum length specified for ‘Name’ field; and input string “<p>thequickbrownfoxjumpsoverthelazydog” can verify both these constraints. It should also be verified by the tester that application does not support anonymous access methods. In case any of these vulnerabilities exists, the application is in danger.

5. Service Access Points (Sealed and Secure Open)

Today, businesses depend and collaborate with each other, same holds good for applications especially websites. In such case, both the collaborators should define and publish some access points for each other. So far the scenario seems quite simple and straightforward but, for some web based product like stock trading, things are not so simple and easy. When there is large number of target audience, the access points should be open enough to facilitate all users, accommodating enough to fulfill all users’ requests and secure enough to cope with any security-trial.

How to Test Service Access Points: Let me explain it with the example of stock trading web application; an investor (who wants to purchase the shares) should have access to current and historical data of stock prices. User should be given the facility to download this historical data. This demands that application should be open enough. By accommodating and secure, I mean that application should facilitate investors to trade freely (under the legislative regulations). They may purchase or sale 24/7 and the data of transactions must be immune to any hacking attack. Moreover, a large number of users will be interacting with application simultaneously, so the application should provide enough number access point to entertain all the users.

In some cases these access points can be sealed for unwanted applications or people. This depends upon the business domain of application and its users, e.g. a custom web based Office Management System may recognize its users on the basis of IP Addresses and denies to establish a connection with all other systems (applications) that do not lie in the range of valid IPs for that application.

Tester must ensure that all the inter-network and intra-network access to the application is from trusted applications, machines (IPs) and users. In order to verify that an open access point is secure enough, tester must try to access it from different machines having both trusted and untrusted IP addresses. Different sort of real-time transactions should be tried in a bulk to have a good confidence of application’s performance.  By doing so, the capacity of access points of the application will also be observed clearly.

Tester must ensure that the application entertains all the communication requests from trusted IPs and applications only while all the other request are rejected. Similarly, if the application has some open access point, then tester should ensure that it allows (if required) uploading of data by users in secure way. By this secure way I mean, the file size limit, file type restriction and scanning of uploaded file for viruses or other security threats. This is all how a tester can verify the security of an application with respect to its access points.

If you enjoy reading this article please make sure to share it with your friends. Please leave your questions/tips/suggestions in the comment section below and I’ll try to answer as many as I can.

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
How to Test Application Security – Web and Desktop Application Security Testing Techniques

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

In this article we’ll be discussing on remaining five important software testing certifications:

1) ISEB & ISTQB
2) CMST
3) CASQ
4) CSQA
5) CMSQ

Here are the details on these certifications eligibility, exam patterns and how to apply guide.

1) ISEB & ISTQB:

ISEB (The Information systems Examinations Board) certification is the step taken forward by a chartered institute for IT called BCS (British Computer Society), to support the career of IT professionals in IT field. ISEM was formed in 1990 which is a division of BCS. This professional certification is available in foundation, practitioner and advanced level to cater the needs of each IT testing aspirant. While ISTQB stands for “International Software Testing Qualifications Board,” and it was formed in late 2002. Both are similar certifications, at the foundation level are same, in essence. The only distinguishing factor is that ISEB is UK specific whereas ISTQB is international certification.
BCS offers following internationally recognized qualification in following subjects:

• IT Service Management
• Software Testing
• Sustainable IT
• Business Analysis/Change
• Solution Development
• Project Management and Support
• IT Governance, Information and Security
• IT Assets and Infrastructure

Following are the levels at which both of these certification are available to suit the needs of every professional:

• Foundation Level – Certification at this level provides the broad coverage about a specific area. This is specifically designed to enhance the knowledge set and future scope of managers. Its cost is £130.
• Intermediate Level – Intermediate level certification exam is focused in examining the subject in more detail which acts as the basis for the practitioner level certification. Its cost is £110.
• Practitioner Level – This level exam lay emphasis on a specific skill within a subject area in a more detailed manner to provide the practical knowledge of IT skills. Its cost is £150.
• Higher Level – Higher level certification is meant for managers and specialists, having deep knowledge of their subject of concern. Its cost is £540.

To apply for this certification exams at any level, click
Apply for ISTQB or ISTQB-BCS

2) CMST:

CMST, short for Certified Manager of Software Testing, is meant to establish the competencies of testing professional in software industry at the international level. Having CMST certifies means acquiring qualification in terms of principles of testing field and capabilities to handle software testing scenarios. The prerequisite of taking this exam includes:

• Having a bachelor’s degree and at least 4 years of relevant experience in software testing field, or
• Having an associate degree and at least 6 years of relevant experience in software testing field, or
• Minimum of eight years of relevant experience in software testing field.

The potential candidates are required to demonstrate their capabilities in following subjects:

• Test Planning
• Test Reporting
• Measurement
• Managing Test Execution
• Organizational Development (both, teams and management)
• Communication (both, leadership and behavioral skills)
• Define, deploy and improve work processes

To apply for this certification test, go to CMST, which is the customer portal for candidates and complete all the formalities by following the easy steps to set up the test. The free for this exam is $450.

3) CASQ:

CASQ stands for Certified Associate in Software Quality, which is focused on quality assurance skills and principles at the fundamental level of understanding. CASQ provides the rapid career progression at a potentially affordable cost. His exam is intended for beginners in quality for all those which have one of the following requirements completed:

• Having 3 year/4 year degree from a certified institution, or
• Having 2 year degree and one year of relevant experience in IS (Information Services) field, or
• Having three years of relevant experience in IS (Information Services) field.

Questions related to following skill set are expected in the exam:

• COTS, Outsourcing, Contracting Quality etc.
• Quality Principles and Concepts
• Quality Leadership
• Quality Assurance
• Quality Control Practices
• Quality Baselines
• Quality Planning
• Metrics and Measurement
• Define, Build, Implement, Improving of Work Processes etc.
• Internal Control and Security

Similar to CMST, the application process is carried out at Customer portal on CASQ. However, this certification is affordable and any aspiring candidate can get certified at $100.

4) CSQA:

Certified Software Quality Analyst (CSQA) certification is an intermediate level exam which is considered as the standard in best practices and principles of software quality assurance in IT industry. CSQA certified candidates are recognized in several business and professional organizations which boost their career growth manifolds. This exam is specifically beneficial for the role of the quality advisor to management. However, it has following prerequisites, one of which needs to be met to be eligible for this exam:

• Having 4 year degree and two years of relevant experience in IS (Information Services) field, or
• Having 3 year degree and three years of relevant experience in IS (Information Services) field, or
• Having 2 year degree and four years of relevant experience in IS (Information Services) field, or
• Having six years of relevant experience in IS (Information Services) field.

Along with the above mentioned requirements, the applicant should be currently working or having at least 18 month of experience, specifically relevant to certification designation.

Log on to the customer portal at CSQA to schedule the exam at the charge of $350 as the test fee.

5) CMSQ:

Certified Manager of Software Quality (CMSQ) certification is an international level assessment for the skills in software quality assurance leaders and managers. CMSQ certified professionals are either working at top IT organizations or soon will join them at managerial post in quality assurance unit. This is the advanced level certification in software quality field and this fact is equally justified by the requirements demanded prior taking this examination, which are one of the following:

• Having a bachelor’s degree from an accredited institution along with four years of relevant experience in software quality assurance field, or
• Having an associate degree along with six years of relevant experience in software quality assurance field, or
• Having eight years of relevant experience in software quality assurance field.

Same as the other quality certifications, this one also follows the same process of application which is by logging into CMSQ, which is the customer portal and acts as the single point of applying. The cost of this exam is $450.

Please feel free to share your experience while taking any of these software testing and quality assurance certifications.

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
Software Testing and Quality Assurance Certifications – Part 2

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

Application Testing is an activity that every software tester performs daily in his career. These two words are extremely broad in practical aspect. However, only the core and most important areas will be discussed here. The purpose of this article is to touch all the primary areas so that the readers will get all the basic briefing at a single place.

Categories of Applications

Whether it is small calculator software with only the basic arithmetic operations, or an online enterprise solution; there are two categories of applications.
a. Desktop
b. Web

For desktop applications, testing should take into account the UI, business logic, database, reports, roles and rights, integrity, usability and data flow. For web applications, along with all these major areas; testers should give sufficient importance to performance, load and security of the application. So AUT is either desktop software or a website.

Application Testing Methodologies

This is a well-known and well discussed aspect; there are only 3 universally accepted methodologies;

a. Black Box: In black-box testing, the AUT is validated against its requirements considering the inputs and expected outputs, regardless of how the inputs are transformed into outputs. Testers are least concerned with internal structure or code that implements the business logic of the application. There are four primary techniques to design test cases for black box testing;

i. BVA (Boundary value Analysis)
ii. EP (Equivalence Partitioning)
iii. Decision Tables
iv. State Transition Tables (and diagrams)

a. White Box: Primary focus of this methodology is to validate, how the business logic of application is implemented by code. Internal structure of the application is tested and the techniques available to do so are;

i. Code Coverage
ii. Path Coverage

Both the above listed techniques contain several other strategies that may be discussed in some other article. Some techniques are discussed in ‘Test Case Design Techniques’ topic.

a. Grey Box: Practically speaking, this is a mixture of black box and white box. In this methodology, mainly the tester tests the application as in black box. But, for some business critical or vulnerable modules of application; testing is done as white box.

Application Testing Tools

According to the best of my knowledge, there are at least 50 testing tools available in market today. These include both paid and open source tools. Moreover, some tools are purpose specific e.g. UI testing, Functional Testing, DB Testing, Load Testing, Performance, Security Testing and Link validation testing etc. However, some tools are strong and provide the facility of testing several major aspects of an application. The general concept of ‘Application Testing’ is its functional testing. So, our focus will be on functional testing tools.

Here is the list of some most important and fundamental features that are provided by almost all of the ‘Functional Testing’ tools.

a. Record and Play
b. Parametrize the Values
c. Script Editor
d. Run (the test or script, with debug and update modes)
c. Report of Run session

Different vendors provide some specific features that make their product unique to other competitor products. But the five features listed above are the most common and can be found in almost all the functional testing tools.

Following is the list of few widely used Functional Testing tools.

1) HP QTP (Quick Test Professional)
2) Selenium
3) IBM Rational Robot
4) Test Complete
5) Push to Test
6) Telerik

Software Test Plan (STP)

For any activity, some planning is always required and same is true for software testing. Without proper plan there is always high risk of getting distracted during the testing. If this risk becomes a fact, the results could be horrible.

Following are the 5 main parts of a good Test Plan:
a. Scope
i. Overview of AUT
ii. Features (or areas) to be tested
iii. Exclusions (features or areas not to be tested) with reason
iv. Dependencies (of testing activities on each other, if any)

b. Objectives: This section describes the goals of testing activity e.g. validation of bug fixes, new features added or revamp of AUT etc.

c. Focus: This section describes what aspect of application will be included in the testing e.g. security, functionality, usability, reliability, performance or efficiency etc.

d. Approach: This section describes what testing methodology will be adopted for which areas of AUT. For example, in the STP of an ERP application; the approach section may contain the information that black box testing will be approach for payroll. On the other hand, for reports the approach will be grey box testing.

e. Schedule: This sections describes that who will be doing what and where on the AUT, when and how. Schedule section is, in fact, a ’4Ws and H’ of the STP. Normally it is a simple table, but every organization may have its own customized format according to their own needs. Once the test plan is ready and application is under development; testers design and document the test cases. In the “Application Testing – Methodologies” section above, I have listed the TC design techniques.

Application Testing Cycles

Once the AUT is ready for testing, the practical phase of testing cycle starts in which testers actually execute the test cases on AUT. Keep in mind that here the testing cycle is discussed regardless of Testing Levels (Unit, Module, Integration, System and User Acceptance) and Testing Environments (Dev, QA, Client’s Replica, Live).

a. Smoke Testing: The very first testing cycle that is wide and shallow in approach. The purpose of smoke testing is to verify that there are no crashes in the application and it is suitable for further testing.

b. Sanity Testing: The second testing cycle that is narrow and deep in its approach. Its purpose is to verify that a specific module is working properly and is suitable for complete testing.

Tip: Usually there is not ample amount of time available to run these two cycles separately. So, a mixture of both these cycles is adopted in practical.

c. Functional Testing: The proper and full fledged testing of application is performed in this cycle. The primary focus of this activity is to verify the business logic of the application.

d. Regression Testing: This is the final cycle of testing in which the bug-fixes and/or updates are verified. Moreover, regression testing also ensures that there is no malfunctioning in other areas of AUT due to fixes and changes.

Bugs are logged in every testing cycle. There is no distinct border line between the testing cycles. For example, in Regression the Functionality is also verified and it may also require smoke, sanity or their merger first.

Application Testing – Best Practices

I think, hundreds of articles are available about this on internet. Every article suggests different number of best practices ranging from 7 to 30 (that I have seen so far). However, I have just 5 tips for readers.

1. Plan Properly
2. Test Keenly
3. Log the bugs Clearly
4. Do Regression Test Efficiently
5. Improve above four skills Continuously

Conclusion: Application Testing is a vast subject and the primary activity of any software tester. In this article, I have provided the overview of some most fundamental and necessary areas that fall under this topic. Application Testing involves strategies, phenomena, approaches, tools, technologies and guidelines. However, I have addressed the conceptual and practical insight of its salient concerns.

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
Application Testing – Into the Basics of Software Testing!

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.

GUI testing can be toughest part especially while testing on smart device. You should pay full attention to the GUI while testing on smart devices and surely it is an important task that deserves significant time and resource allocation.

Practical Tips for Testing GUI on Smart Devices:

For me, while testing GUI, all the controls are accused. I raise questions why they are there on the screen and I try to answer these questions. I argue in opposition and favor of the controls one by one and I do all this without discussing with someone else. It is the time when I’m wearing multiple hats, Controls are accused and I’m the Prosecutor , I’m the Defense Lawyer and I’m the Judge and during all this process a control must have valid and solid reasons in its favor to be there on screen and consume space. I suggest you to try it and it will help you to decide which controls to display on the screen.

There also come the situations where you are given an already built GUI to test. In such situations also think about the missing controls, the controls that will add value to the screen and compare their importance with the current ones. If you think you need to make a change go ahead.

Once you have decided which controls will be shown on the screen, think thoroughly about size, style and location of the controls on the screen and more important how user will interact with them?

3 important factors to be considered while testing GUI on Smart Devices:

Size:
There are too many variations in screen sizes and available resolutions. In smart devices especially, controls sizes are not static, they have relation to the available screen size.

While testing, make sure that controls size looks esthetically good and control is completely visible on the screen without any scrolling. Test the GUI on different devices with different screen sizes and resolutions.

Emulators are good for this purpose but nothing matches the real device. So make sure that you test on at least two or three real devices. Also don’t forget to test on landscape and portrait orientations if the device supports it.

Style:
Definitely your application has a specific design. And style of the controls should match with that design. You might have seen many applications where some controls e.g. panels have round edges and text boxes in them have sharp edges. Although this type of issues don’t affect the usability or functionality but still a consistent look of the application helps to build a friendly relation between the application and the user.

Relatively more important thing in style is font on the different pages. Most of the times, we focus the text that is visible in normal situations and ignore the text that appears in specific situations. Success and Failure messages are an example of such type of text.

Another factor, important in style is relation between the font color and the situation in which text is displayed. For example Red color is used for Error messages, Green for success, Yellow for warnings and Blue (now a day occasionally) for hyperlinks.

Location:
Location and position are the two words that are used alternatively and it is interesting that they are further used to convey two different concepts that are explained below.

1. Sometimes it is the area on the screen where a control appears. For example Header is located on Top of the page, Labels are Left Aligned, and Text boxes are Right Aligned etc. Here text in bold are relative positions of the controls

2. Sometimes it is the order of a control among the other controls. For example while getting personal info, First Name is followed by the last name or format of controls to ask for a US address should be in order ZIP, City, State.

For both these situations, make sure that everything is logical and shows a good aesthetic sense.

Forgot something even more important. There are situations where one or more controls appear on more than one screen, in this situation make sure that they appear on same location and in the same order on all the pages.

This is a guest post by Uzair Baloch. If you want to write one, please read the guidelines.

About Author: With an industry experience of 3+ years, Uzair Baloch is currently working as Sr. SQA Engineer for a Canadian organization in their offshore office.

Hope these tips will help you testing GUI on any smart devices. If you have more ideas please share with us in below comments.

---------------------
I just wanted to thank you for subscribing to SoftwareTestingHelp.com. This blog is a success because of you and your support. Here's to your success!

As always, I appreciate your valuable comments. Visit below link to post your comment:
GUI Testing on Smart Devices – Testing Guidelines

Thank you so much! ---------------------
Recommended: TestLodge - Online test case management tool - Web based test case management software allowing you to manage your test plans, requirements, test cases and test runs with ease.