The more we fine tune our application the more the test engineers are going to use it.If our Framework supports Negative testing ,their is nothing like it.Manual persons also can jump into our framework to speed up their application testing.It is nothing but to increase our coverage i.e Automation Coverage This simply saving manual effort.
6. Clear Expectation:
Prepare a capability analysis of the engineers who are working in the team. second,prepare an estimation of the scripts according to the complexity[may be simple ,medium,complex,very complex]. Now set an target like in a day ,how many simple,medium,complex and very complex you can deliver.Estimate accordingly. I would suggest take 1-2 days buffer while planing and provide estimate accordingly.
Second important aspect is to get transparency. Yes. depending upon the maturity of the employees , we must be transparent to them. Information is power in our IT industry. In few cases, it is seen that the information is not shared to the team. Manager or lead poses to be over-smart thinks that this act gave them lot of power. Actually this is a poor managed team where actually nobody knows where the project stands.
The best approach is to divide and rule approach. Look at your requirements then identify the smaller requirements. Now identify the smallest unit testcase that can be automated. Once this identification is done,look for reusable functions,common approaches. Build the helper functions. then start automating with maximum re usability. In this way, many automation testcases can be automated within very short time.
Next to make test inventory scale-able and maintainable always depend on test data. Use testdata for triggering and running large scale testcase. There are many approaches to get or generate test data. But framework should support multiple format like-CSV,Spreadsheet,text file, random generation,xml. etc.Plug and play with these data source can give your test framework wings.
Top Ten Strategies to Make Test Automation As a Service
Use different tools to understand the progress in milestone by milestone manner.Budget control,statistical tools like six sigma,lean,Failure analysis,Fish-bone, process control ,key performance indicators,regulars,Standardized reporting should be used to analysis different scenarios.
Retrospective meetings should be well prepared rather just jotting few points and go unprepared.
Every claim good or bad should be supported by supporting data.
Capture all is the key for a successful framework.Always capture Step information,log,Success criteria,Exit and entry criteria and Error Information.
Now a days testing demands very fast execution and report generation.Please refer one of my post on Having Repository.So now a days people like to have a pattern based testing where there will be no Object Repository.Pattern will detect the type of field and will do actions.
What are your choices for software package testing
Unbiased testing denotes the check structure and implementation most properly performed by someone who is autonomous from the staff of builders. This indicates that the benefits will be impartial and mirror an aim view of solution’ abilities.
But whilst enterprise literature offers the great time and dollars preserving features of outsourcing delicate. testing – when stressing superior high quality operate you can count on – one need to choose plainly if it is genuinely helpful to outsource computer software screening.
How can you determine if it would make sense to outsource smooth. testing? You’ got to start out by meticulously examining your requires as they relate to this critical section of computer software improvement. Tender. screening indicates numerous things to numerous people today. The principal objective is to guarantee the software package features as specified right before heading into production. But it also signifies producing certain the program is intuitive and simple to use.
Top Ten Strategies to Make Test Automation As a Service
Just before you make the choice to outsource delicate. testing, it’ vital to explain what you want from the outsourcing business. As their reputation grows, so do the expert services these organizations give. Several also provide software program style companies. Or, they will strategy, but not put into practice a software tests procedure for your organization. And they will even deliver men and women to your web page to take care of integrating the delicate. testing resources you obtain with your components. In standard, regardless of your actual comfortable. screening demands, if you’ acquired the dollars to pay for it, you’ come across an outsourcing enterprise ready to do it.
In automation industry , we have two categories of test engineers.
1. Designer- Mainly Test Architect
2. Automator- Who will automate the test.
Automators are multi talented like a developer. They need to understand the requirements, create test case,create testscript,create supporting testdata, execute the test,analysis of the failures,re execution, reporting. So it is always better to have programming knowledge in automators.
How many engineers need to be hired depends on the load of work you will have. If the project follows waterfall model,you will get sometime to take a look of the work and estimate accordingly. But if the project follow a agile , then it is tough to get the projected load. So it is always better to have one or two shadow worker in buffer.Most of the companies now are creating talent pool.A pool of engineers with required skillset.
As I said earlier , It is no more a manual test engineer’s job to automate application,It requires dedicated automation developer now a days. Apart from a dedicated team,the automation team requires a manager or a technical architect to drive the team. They should be from automation background. If the hiring is not correct way, like a manual test engineers given automation responsibilities or a manual manager is guiding automation team, then in most of the cases team lacks of motivation and innovation.
9. Operational Model:
As in agile methodology the load of the work is little unpredictable and requirements may get changed. As a result the traditional operative model of billing[Hours calculation,timesheet entry] may not work for both the vendor and client. In this changing moment of software development it may be good to go cloud’s way of billing. Deliver the agreed quantity and get the billing. It is always a win win situation for both the parties as it follows pay as use mode. This solves the not used,un billable resource problem. I have seen some model like the total no of scripts delivered, number of test execution happened,number of regression run,number of bugs logged.So according to your model,use quality center or jenkins to create more demand ,execution,daily execution,report to earn more.