Category Archives: Test automation process

Continuous test automation planning during Agile iterations

Continuous test automation planning during Agile iterations

Please refer to my blog and videos on Agile practices and the importance of Re-usable code libraries for cycle time reduction.

During the reusable code usage and the iterations or sprint planning, the test automation also can be planned, designed and implemented.

This blog eloborates on  the easy processes can be used to implement it and demonstrate the cycle time reduction. Please note atleast after passing the two cycles of tests on the selected manual scripts need to be planned for test automation.

I am trying to elaborate on the process of the Automation of unit testing and component or module integration test automation. Please note the test automation is also a development project. Hence some of the phases are similar to SDLC. The pictorial chart elaborates the detailed steps involved in these test phases automation. Module (Unit) or Component Development in Agile: The below contents and the chart narrates the relationship of automation Development process and the Testing process under each development phase. Development and Testing process Relationship table:

Phase Development Process Test Process
Module (Unit) or component Development Design module from requirements Perform test planning and test environment set up.
  Code module Create test design and develop test data.
  Debug module Write test scripts or record test scenario using module.
  Unit test module Debug automated test script by running against module. Also, tools that support unit testing [Purify, etc] can be used.
  Correct defects Rerun automated test script to regression test as defects are corrected.
  Conduct Performance Testing Verify system is scaleable and will meet the performance requirements. This is the entry criteria for Integration test automation.
Integration
Build system by connecting modules.Conduct Integration test with connected modules.Review trouble reports. Combine unit test scripts and add new scripts that demonstrate module inter-connectivity. Use test tool to support automated integration testing.
  Correct defects and update defect status. Rerun automated test script as part of regression test, as defects are corrected.
  Continued Performance Testing Activities At this point, Verifying system is scaleable and will meet performance requirements with the integrated modules. If this passes then the system test or VVT entry can be considered.

Below chart demsontrates the process steps to be used for test automation of unit test and integration testing:

UT&IT

The acronyms used in the chart: TC–>Test case, TD–>Test data, TR–> Test requirement, UT–>Unit test, IT–> Integration test.

All the automated test scripts and test data  need to be preserved under configuration management tools.

Choosing the right tools for test automation comes under tools evaluation process. Once the tools are identified, the above processes can be planned and adopted for regular practice on the Agile projects.

 

 

Vcard-Shanthi Kumar V-v3

Data migration testing practice – A Kindle edition

 

 

 

Data Migration-image

Background on writing this book:

Most of the data migration projects can happen through the incremental data loading or if they have redesigned any of their business applications data migration need to be verified to give confidence level to the business users. Sometimes it is a critical activity and risk involved towards certification of the migrated data for business.

Many of these project timelines are getting extended or some failures are happening due to lack of; knowledge, best practices and the experiences or following right approach.

To overcome on the above situations and to be proved as best IT professionals in front of the business user community, we need a methodology and the right approach to conduct successful data migration testing and certify the data for business.

This book has been written with 10 plus years of testing experience on this kind of projects by suggesting the feasible approaches, practices and easy teams handling with right and ontime delivery by involving business users also. It also can reduce the risks while doing continuous planning improvements.

Different charts or diagrams can help the reader to understand the process faster also. One of the charts presented below:

Some of the Contents are:

Chapter 1: Introduction

Chapter 2: The scenarios of data migration

Chapter 3: Requirements Analysis

Chapter 4: Testing practices for data migration

Chapter 5: During data discovery phase

Chapter 6: Identifying the Business scenario based data

Chapter 7: Identifying the relevant data schemas

Chapter 8: Identifying the tables/queries/SPs, etc. on each of the Data schemas

Chapter 9: Planning for each Data schemas Extraction, Transformation and Loading to target Applications.

Chapter 10: Verifying the source and target data flows for business operation continuity.

Chapter 11: Conducting data verification and validation by QA/Testing team

Chapter 12: Planning

Chapter 13: The project approach

Now it is in cheaper price  look into it if you are on the same practice.

URL:http://www.amazon.com/Data-migration-testing-practice-incremental-ebook/dp/B018EP9MO2/ref=sr_1_2?ie=UTF8&qid=1452042282&sr=8-2&keywords=Shanthi+vemulapalli

If you feel these practices can be used by somebody please leave your comments after reading the book.

 

 

 

 

 

 

Coolpad Note 3 (White, 16GB)

Apple iPhone 4S (Black, 8GB)

Lenovo S850 (Dark Blue)

Kindle Voyage Wifi – 6″ High-Resolution Display (300 ppi) with Adaptive Built-in Light and PagePress Sensors

 

 

The effective software test automation process

Test Automation - Process

During the DevOps practices, it is mandatory for the Developers, Test engineers and DevOps engineers to implement the test automation using the automation tools.

So every test engineer need to know the process related to the test automation. Through this blog I thought of sharing the process.

 I used this methodology during traditional project management and also during Agile project management. It was very successful and the relevant clients were astonished with these methods being followed by me and my teams by convincing them while using and implementing these practices. We also got very good CSAT ratings.

Please note you need to educate the client team in advance on your process steps by mapping them to your environment. Otherwise, they might feel it is a bookish knowledge you are trying to use it.  

During agile testing you can devise the test requirements into a Sprint planning and conduct the demos to the development team and the stakeholder teams also. If it is feasible for you, you can also try and let me know for a POC.  

This blog has been enhanced as per the request of the global readers of this site and it has been posted in the following link under PPT: https://flevy.com/browse/business-document/effective-test-automation-process-in-practice-1356

NOTE: Please keep watching this blog site for some more useful blogs for your daily worklife of IT Journey.Vcard-Shanthi Kumar V-v3