Skip to main content

Managing Software Project Failures

Software Engineering is yet to find one solution where probability of success of meeting all objectives are high. Even though there are many research happening, people are still believing in process fine-tuning as one of the solution. The current trend is to adapt agile methodology with shorter sprint cycle of delivery to get customers feedback faster. Tool penetration in the Software Development Life Cycle also reduced human errors, improved productivity and reduced variance significantly.  This is one engineering field where tools are still evolving in each phase. Success in one phase is making people control schedule, quality and cost variance in projects significantly. That phase is functional testing phase. 

In this blog I would like to share some of the challenges in functional test automation and approach which worked for me while consulting organizations. 

I summarize the challenges I heard which you may hear in some of your current business situations. 
  • Number of planned releases to system testing team and actual releases have huge variance
  • There is a feeling that certain issues in software should have beeen caught earlier in the life cycle
  • Test cases are in place why are we not automating test execution? Which framework to adapt? Which tool to use?
  • Our solution is complicated we have many environments on which we need to test and there is no single framework which helps Web UI testing, API testing, Database Testing and Mobility testing
  • Why are we not using the same testing team who are testing currently, contribute for test automation effort also?
  • We did automation using some framework but changes to product was so much we could not sustain script maintenance speed resulting on scrapping many of the scripts which were working earlier
  • Metrics we collect looks too much but we are unable to answer some of the stake holders questions during project review 
So the search continues for one technical solution which will address many of them. I was also looking for such solution to recommend to my client and I found in a framework created by young engineers who had captured all challenges of test automation project failures very nicely and had addressed all of them in their framework. The people associated have used this to create young highly productive engineers who are 3 times faster in converting test cases into automated scripts, have capability of doing POC in a shortest time due to 90% of the object handling required libraries they have in their framework. The same framework supports API testing, Database testing and mobile side both Android and iOS applications.

The automation should support continuous integration and ensure high quality release to system testing team and later to production. Regression automation % also continuously should grow enabling faster cycle time to production release with reduced defect escapes. The percentage of projects  not meeting the set objectives must reduce drastically towards zero.


Comments

Popular posts from this blog

Lock down a new experience

Did we learn anything from this Covid-19 forced lock-down? I thought many of us experiencing something which we never experienced in our life so far. Let me share what I am going through in my first blog of this series, it may encourage people to share what worked for them so collectively we may get ideas on how to prepare to handle situation when lock- down is removed. Before lock-down After lock-down Get up at 6:00am go for yoga class between 6:30 to 7:30am. Read NEWS paper, get ready, neatly shave beard (though it looks like not required every day) and wear nicely ironed clothes, have breakfast, pack-up my lunch box and leave for office at 9 am. Reach office by 10:15 to 10:30am. Stand-up meeting with leadership team and get onto my daily planned activities. (We have/ sorry had 😊 a cook who comes at 6:00am and used to prepare breakfast and lunch to take for office). Get up 6:30am and help my wife in preparing some breakfast, squ...

Life of automated tests

Automated Test Need Maintenance What stakeholders hate to hear is the news "Automated test will not work in this environment need maintenance". In the current industry trend many organizations will manage multiple versions of code going through different kind of changes or unique configurations settings. I am sure many of you in test automation area may be looking for one tool which supports sustenance of automated tests % while product is going through changes,  When to start focusing on test automation? Some industry veterans recommend to look at automation effort only when product is stable. But some people say automated tests always increase speed of going to market  so start anytime it is worth. Who is right? we are not sure. But challenge of sustaining automated test % in a given environment is always there for all of us.  Multi stage of product  A build developed goes through development environment, QA environment, Pre-production environment...