onPrepare: async function () {
Quality Process Analyst | Tools Management | Technology Management | People Management
Tuesday, September 3, 2024
WebdriverIO onPrepare To check Url
WebdriverIO Chrome Browser Capabilities For Windows & Linux Environment
],
Friday, December 8, 2023
This is a simple representation, and the actual workflow might be more complex based on your team's specific requirements and processes. Customize the workflow according to your team's needs, and consider integrating it with your version control system and other tools for a seamless development process.
Thursday, December 7, 2023
Calculate Software Automation ROI
Data Calculation parameters:
- Number of test-cases can be automated: (B5 -(B5*B6)/100)
- Automation of the test-cases needs: =(($B$7*$B$11)+B9)/B12
- Time-to-market acceleration: =(B10*B7*B8)/8
Statistics calculation parameters:
Saved manual testing time (accumulated), hrs =
- =$B$10*F21*$B$8*0
- =H21+($B$10*F22*$B$8) ...
Automation costs (accumulated), hrs =
- =D21
- =D22+I21 ...
Autotests run and support cost, hrs=
- 0.00
- =$B$13 ...
Test cases automated =
- =IF((E21/$B$11)*B12 >= $B$7, $B$7, (E21/$B$11)*B12)
- =IF(((E22/$B$11)*$B$12) + $F21 >= $B$7, $B$7, (($E22/$B$11)*$B$12) + F21) ...
Autotests development cost, hrs using standard working hrs/month =
- =IF($B$14 <= $B$18 * $B$12, $B$14, $B$18*$B$12)
- =IF(SUM($E$21:E21)+$B$18 >= $B$14, MAX(0, $B$14 - SUM($E$21:E21)), $B$18*$B$12) ...
Automation costs, hrs =
- =E21+G21
- =E22+G22 ...
Saved manual testing time, hrs =
- =$B$10*F21*$B$8*0
- =$B$10*F22*$B$8 ...
ROI, hrs =
- =H21-I21
- =H22-I22 ...
Total saved in $ (- ve means in loss) =
- =(B45*B17)
Sunday, February 6, 2022
Short Continuous Deployments To Production !
One of my product teams has been successful in deploying to production once every 4 weeks. In the past, our release plan would comprise of an Iterative and incremental development sprint zero, one or three working sprints, one or two alpha or beta sprints, and followed by a hardening sprint.
We were essentially releasing features to end-users once in every six 8 or more. Our product features are critical to the business.
Our product team migrated to a shorter release cycle thereby developing and deploying for each sprint and changed to following into 1 month cycle,
Benefits of Small Releases
As the iterative development process is mastered, the door opens for the team to deliver smaller and more frequent releases to the end-users, and that is one of the prime drivers of agile. The ability to release software more frequently has two primary business benefits: increased responsiveness to the customer amidst changing marketing conditions and reduced risk to the enterprise.
- Frequent deployments to end-user provide a competitive advantage.
- Product requirements could change significantly if deployed to production once every few months. By launching frequently, you could gather data from end-users earlier and apply adjustments accordingly.
- Keep your team energized and motivated.
- Helps in establishing best practices.
- Exposes risks and challenges with design, architecture, and solutions earlier in the process.