Monday 1 September 2014

Scenarios which are preferred/not preffered for automation testing

Scenarios which are preferred for automation testing:

In general scenarios which are complex and more repeatable those are more suitable for automation testing
Ex:
                  -Sanity Test scenarios
                  -Regression test scenarios
                  -Scenarios which are required multiple set of test data to validate (i.e. Re-Testing)
                  -Compatibility Test scenarios

     Scenarios which are not preferred for automation testing:
In general scenarios which are simple and which are not repeatable those are performed manually only
Ex:
                  -User Interface test factors
                  -Usability test factors
                  -One time testing activities
                  -Ad-Hoc testing/Random testing activities (i.e. Informal testing)

    Note: For an application there can be manual testing team and automation testing team but automation                    testing is an optional

Automation Testing


Automating human activities (i.e. TC's execution) in order to validate application is called automation testingAutomation testing can be performed using programming languages (ex: C#) or Scripting languages (ex: Perl Scripting) or any one of the 3rd party automation tools like QTP, WinRunner, Selenium…etc

Advantages:
-fast in execution
-more Reliability
-More Consistency
-Automation scripts are Repeatable
-Automation scripts are Reusable for different versions of application

Disadvantages:
-Tools are expensive/costly
-Skilled Automation TE’s are required
-it is not possible to automate all the areas of application


Friday 31 January 2014

Globalization, Internationalization and Localization in Software

What is Globalization, Internationalization and Localization in Software Testing?

In Today’s competitive world many of the clients are targeting the global audience, which means going beyond borders and working with clients to make sure application has proper global sets in terms of functional, readable, and viewable in multiple platforms and cross-browsers. Along with that there are many languages in the world, so in this situation do we need to create a separate application or website for each languages & countries? The answer is NO. This can be accomplish by simply doing the code in such a way that changing the text in the file they can localize the product in any language & this type of testing is called as Globalization (Internationalization) and Localization Testing.

Summary of what is mean by Globalization, Internationalization and Localization Testing?

  • Translation is one part of Localization
  •  Internationalization is a pre-requisite of Localization
  •  Internationalization and Localization are parts of Globalization
  •  Globalization includes many business-related activities outside of the product itself.

 What is Globalization Internationalization and Localization?

Aim of Internationalization and Localization testing is to make sure usability, acceptability, reliability to audience and users worldwide & check whether the application under test is ready for world-readiness. First application under test needs to be localized & then tested for many other counts like locale, copy text, language, compatibility, reliable functionality and interoperability.
What is Globalization (Internationalization) Testing?

Globalization definition: Globalization Testing is testing process to check whether software can perform properly in any locale or culture & functioning properly with all types of international inputs and steps to effectively make your product truly global. This type of testing validates whether the application is capable for using all over the world and to check whether the input accepts all the language texts.

It is also called as “G11N“, because there as 11 characters in between G & N. It ensures that the product will handle international support without breaking functionality. Globalization testing mainly focuses on the functionality of the product with any culture/locale settings and every type of possible international input. It also helps uncover issues that may increase the costs of localization and future product support later on.


Localization definition: Localization testing is testing process to validate whether application is capable enough for using in a particular location or country. In this testing localization, testing is to carried out to check the quality of the product for particular locale/culture.  To check the quality of translation in localization testing, we should request local staff as well. It is to be carried out to check the localized version of the product, For example: French product for French users. It is also called as “L10N“, because there as 10 characters in between L & N.

Let’s see another example of a Zip code field in Sign up form:
1) For globalized, it should allow to enter alphanumeric inputs
2) For localized (country like INDIA),  it should allow only numbers in input field.

One more nice example of Localization:
Localization Example of Steering Wheel

Localization Example of Steering Wheel



What we need to test in Internationalization or Globalization?

Check for the functionality with different language setting. It might possible that functionality may not work other than English setting. Here is one example of API which cause problem in the communication between Consumer and Owner. In the API, they forgot to make agreement for data format, one is using English language & one is using local format.
    Check if no any hard-coded string use in the code. You can test with the different language by changing the language setting from Computer.
    Check the Numbers, Currencies, Character sets for different countries.

Benefits of for Localization and Globalization Testing

    It reduces overall testing costs
    It reduces the support costs
    It help to reduce time for testing which result faster time-to-market
    It has more flexibility and scalability.

Conclusion: The Localization Testing and Globalization testing is done for adapting a product to a local or regional market & it’s goal is to make appropriate linguistic and cultural aspects of product. These testing performed with the help of by translators, language engineers & localizers. Now we understand the importance of Localization Testing and Globalization Testing and the risk if we don’t have this type of software testing. It is very much important to execute the Globalization Testing and Localization Testing in international product.




Monday 27 January 2014

Traceability Matrix or Requirement Traceability Matrix


What is Traceability Matrix(RTM) ??

Traceability Matrix (also known as Requirement Traceability Matrix - RTM) is a table which is used to trace the requirements during the Software development life Cycle. It can be used for forward tracing (i.e. from Requirements to Design or Coding) or backward (i.e. from Coding to Requirements). There are many user defined templates for RTM. Each requirement in the RTM document is linked with its associated test case, so that testing can be done as per the mentioned requirements. Furthermore, Bug ID is also include and linked with its associated requirements and test case. 

The main goals for this matrix are: 
  1. Make sure Software is developed as per the mentioned requirements.  
  2. Helps in finding the root cause of any bug.  
  3. Helps in tracing the developed documents during different phases of SDLC.


Levels Of Testing

Levels Of Testing

Levels of testing include the different methodologies that can be used while conducting Software Testing. Following are the main levels of Software Testing:
  1. Functional Testing.
  2. Non- functional Testing.

1.Functional Testing.
This is a type of black box testing that is based on the specifications of the software that is to be tested. The application is tested by providing input and then the results are examined that need to conform to the functionality it was intended for. Functional Testing of the software is conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements.

There are five steps that are involved when testing an application for functionality.
Step I - The determination of the functionality that the intended application is meant to perform.
Step II - The creation of test data based on the specifications of the application.
Step III - The output based on the test data and the specifications of the application.
Step IV - The writing of Test Scenarios and the execution of test cases.
Steps V - The comparison of actual and expected results based on the executed test cases. An effective testing practice will see the above steps applied to the testing policies of every organization and hence it will make sure that the organization maintains the strictest of standards when it comes to software quality.


  
2.Non- functional Testing

  1. Performance Testing
  2. Load Testing 
  3. Stress Testing 
  4. Usability Testing 
  5. Reliability Testing