Sunday, September 1, 2013

Test Succession Analysis Method

The term succession means act or process of following in order/sequence, In our context of Software testing it is about understanding how the exist feature in the system take shape in every project version, Succession Analysis  is a Test Analysis method which can be followed during Analysis Phase of the  Project . It primarily involve step by step approach in identifying the base feature impact from  new customer requirements. , So it is in other words analyzing  the Successive behavior of  Exist feature in the project.

This method help in identifying the impact of exist features, deriving  the regression suite and regression effort required for the Testing Project.

During the initial estimation and analysis phase of Test Project life cycle, the succession analysis need to be performed with respect to scope of this project, In Agile , this need to be performed in Iteration 0.

Test Succession analysis feature flow comprise of Inputs , and Process (which we can call as Analysis points) and Outputs




Inputs for succession analysis involve Feature Details such as Feature ID, Feature Name, Description and related Test Artifacts , Customer Scenario/Scope , Feature Usage etc .

After consolidating the input requirements, following  Points need to be considered  for the Succession Analysis of Base feature

        -> PRIORITY
        -> CHANGE MODE ANALYSIS
        -> FAILURE IMPACT
        -> FEATURE MATURITY

Each analysis points above give different dimension to the successive nature of exist base feature of your system/product.
   
Description of Analysis Points

Priority  -
          This parameter denote the priority of the feature for THIS Customer in THIS Project,   it means, feature may be critical in nature, but for the given scope of the project, the priority may vary. So based on the scope of the project priority of base feature need to be updated.

Change Mode Analysis-

             This parameter need to be checked for following characteristics about whether exist feature is changing for the new requirement,it has 4 modes
           
            Change-Independent - which means this feature is changing, but it is independent feature, not impact other New/Base feature,
         
             Change -impacted - which means this feature is changing and also impacting other feature,
            
             Impacted - means this feature not changing , but impacted because of new /exist feature change, 

             Independent - means no change, no impact

Failure Impact-
            This parameter need to be covered depend on impact of the feature failure to the customer, If this feature fail, how much impact it can cause to the customer or to other successive feature,

Feature Maturity -
            This parameter need to be analysed from two factors,
One is  what is the usage of this feature,whether is it used by different customers, and whether is it commercial use or mainly in alpha/beta usage. This analysis give detail of usage of this feature,

Second method is what is test history of this feature, whether detail testing happened for this feature or only moderate testing is carried out so far.

Based on the Analysis of above parameters  Future test Strategy and Regression Test Suite of which feature need to be covered and how much of testing and its estimation are derived, This we can call as Results of Succession analysis.

Results of Analysis -

  Test Succession Analysis Result

 This can be primarily determine how much testing required for the base feature in the current version, it can vary from 0-100%,  , Consider a case, the test maturity of some base feature is very less, and also failure impact is high and priority is also high,  Even this Base feature is independent or no change,  It need be considered for 50% of test in the current version.

  Subjective comments -

In addition in to identification of how many test case of base feature need to be tested as part of regression, few high level analysis inputs can be added, This is subjective comment which can cover what topology or scenario need to be covered for this feature, or any other special comments can be added as analysis inputs.

After each of the successive base feature, is analysed, the results are  taken as input for project test estimation, project test strategy and also input for test design analysis, schema definition.
       
Template Reference

You can check the template for reference in attachment.
https://drive.google.com/folderview?id=0B_yKwLxCSPfVUFlyUnBMdDRtQTQ&usp=sharing&tid=0B_yKwLxCSPfVWjAzcE9jOVpxQkU

Conclusion -

Test Succession analysis is important analysis technique which can be followed by test teams .This method give high value addition in terms of impact analysis of  base feature coverage and justification of regression estimates of test projects .






Mobile Application Testing


Key Difference and Biggest challenge to testing of Mobile Apps is lots of devices involved, and  testing in various devices needs different techniques, technology and resource., we will start with Functional aspect first

Functional Test/App on Device angle -

how you can get access to multiple devices[For Device testing] and technology for test Mobile Application

Some options and  suggestions are

1.1 Can use Emulator to verify basic operation
1.2. Acquire as many friends as possible with different devices
1.3. Remote Lab for testing
1.4 Join the Social Community on Mobile Application test

On above we can check more at 1.3 and 1.4, and 1.1, 1.2 are left to testers choice...

Remote Lab for Device Simulation –

(FREE) Choices first

SAMSUNG LAB.DEV-Samsung   offers a free remote lab web service, called Lab.Dev. It includes some Windows Mobile devices and Android Devices, Lab.dev is a remote test lab service. You can test your developed application in the same environment of real device through Lab.dev.
Nokia Remote Device Access-
Forum Nokia offers a free (yes, free!) remote lab solution for Symbian and Maemo devices called Remote Device Access (RDA), shown in Figures Figure 1 and Figure 2. To use the service, you can accesshttp://www.mobilexweb.com/go/rda (you’ll need to have already created a Forum Nokia account). You will need Java Runtime 5.0 or newer, because RDA is a WebStart Java application.
Still no Free Test Lab Options for ios , if any get info about this, please share
(PAID)
Most Popular ones
Keynote Device Anywhere

Perfecto Mobile

Below sites give clear comparison of both and its pricing


Popular Mobile test community-
 one must subscribe into their forum/blog for continuous update 

(http://www.mob4hire.com) Mob4Hire is a mobile social network aimed at joining testers with mobile devices around the world and developers who want to test applications or websites using a payment service. You can search for testers by country, operator, and device to access the devices you want.

mobiForge is a mobile development and design resource site run by the mobile domain registry, dotMobi. Its stated purpose is to help stimulate the growth of the mobile web by providing technical resources and tools to educate the mobile development community. The site is run independently of any one mobile operator or manufacturer, and as such the content carried is operator and manufacturer agnostic.

-Crowd based testing and SAAS platform [one of the largest] in Testing area[this include Mobile Application test , Not only this]

Recommended Reference –


this presentation from gopinath.jayamalra cover more elaborate detail on Mobile Application test one should refer to..