Technology: VB, ASP, C#, .NET, SQL Server, MVC. WEB api, Boo, XSLT, XML
Automation Tools: Squish
The Support and the QA team work individually and come together only for specific circumstances. When the application has issues, then the support team and the QA team would get in touch with each other to resolve the issue. The QA conducts the necessary tests and works on the issues brought by the support.
The main objective of the project is to work and give a lending hand to the employee benefits application that was developed in Microsoft technologies.
There were massive applications consisting of 120 screens and 30 modules. Moreover, another hassle was that it consisted of nearly 1000 users and 20,000 everyday batch operations.
The initial process was assigning a solid technical team to manage the entire application process. They were assigned to get a clear view of the application code so that they could provide constant and daily support in regards to the SLAs. Then the QA team was formed to automate the regression testing cases.
Selenium Automation for Non-Life Product
Industry Vertical: Non Life Insurance
Domain: Fintech: Property & Casualty
Duration: 6 years
Team Size: 5
Technology: Developed using Java EE, Liferay portal, Jboss & Oracle DB
The hassle of the manual testing process can be effectively replaced with functional automation testing. The importance of functional automation relies on giving quality leads at the end of the process. Moreover, the struggle in running the application can be efficiently addressed by functional automation leading to quality testing every time.
The scope was to own the client’s Property & Casualty product testing end to end.
The main issue was the multi-vendor development environment. The reason for it would be the continuous requests for change and the short certification window.
The initial approach was to initiate an advocated test-driven development. Then the acceptance test reports were written. After these initial processes, the tests were automated. For the purpose of automated runs, the tests were then integrated with Jenkins.
QA Team Achievements
The sanity test cases were automated. Moreover, 90% of the regression test cases were also automated. The acceptance test was conducted for the new features, and these are promptly sent to the team before the release of the code.
Cloud and DevOps Optimization
Industry Vertical: Banking & Finance Domain: Fintech Duration: 12 months (ongoing) Team Size: 25 Technology: DevOps (Terraform, Docker, Kubernetes, Jenkins), AWS, C#, MongoDB & MySQL Methodology: Iterative
DevOps automation is one of the critical processes that need to be followed for every DevOps optimization. Automation is necessary for DevOps as it not only monitors the application but also generates the code to help in the production. With the DevOps automation tools, one can seamlessly maintain the IT infrastructure of the organization.
The aim is to attain cloud and DevOps optimization. However, it is necessary to process test automation with automated deployment to attain this.
The client’s challenge was complex as the present infrastructure was multi-tiered, with various products that had both internal and external integrations. Moreover, the architecture of the infrastructure was quite complicated. It had technology that had induced the latest tools as well as the 20-year legacy tools that made the entire process a little complicated.
Future Focus Infotech’s team did in-depth research and maintained the infrastructure. Moreover, they also automated and optimized the workflows. Then the necessary tools were built for the purpose of UI and API test automation. These tools were built for various products. To attain automation entirely, the CI/CD pipeline was laid.
The huge success was the complete maintenance and optimization of the infrastructure. Moreover, most of the development teams received great support functions in the enterprise. After the implementation of the test automation, the deployment was reduced immensely than before and has led to faster time to market. Moreover, the applications seem to have been seamlessly developed and deployed after the automation workflows. The maintenance was the hectic trouble that was addressed in this process. There is constant tracking and monitoring, and if there are any issues in any of the services, the client can get alerts and notifications to resolve the issue beforehand.
The QA and development are worked independently and simultaneously. As the development team works on features, it would move to the QA for the testing process. So, the QA and development team go hand in hand and work together in bringing out the success of the system. Both these two processes play a vital role in the creation of software and technology. The process adds an added advantage to the system making it an essential part of the technology development process.
The new technology had changed the aspect of the existing one. So, it was necessary for the client to rewrite the existing BenefitBridge application according to the new technology. The purpose of this would be to connect carriers, employers and enroll the employees for the benefits.
The challenge that awaited the client was the migration of the new version to the existing code. The main reason for the initiation of the migration was that the new version was developed in a phased manner. Moreover, there is also dependency on the existing code. Another challenge was posed for the end-users. They would have to learn about the new UI at the earliest. Moreover, they should also get familiar with both the UIs so that they can work efficiently for a certain period of time until the new version is entirely replaced with the code.
The initial process was to rewrite the various applications and the decision support systems that were a great help to brokers, employers and employees to work with the complex system. Then moving forward, the next step was to rewrite the logging and feedback system. This is for the purpose of finding errors and anomalies and correcting them at the earliest possible.
QA Team Achievements
The entire team was able to gather and document the domain-specific test cases. The test cases were a success as they tested the systems and the integrations. The team could now conduct performance and security testing on every major release in the system.
P&C – BI Reports and Dashboards – Dev & Maintenance
IndustryVertical: Insurance Broker
Domain: Property and Casualty (PL/WC)
Duration: 13 years
Team Size: 3 to 6
Technology: SAP Lumira, SAP Crystal Reports, SAP WEBI, SAP Dashboard, Universe, ETL
Platform: SAP BOBI/BODS
BI testing and Dev are great ways to manage the enterprise dashboards and reports. The BI testing works in understanding and analyzing the various graphical data so that efficient business decisions can be made at the end of it. The Dev testing is set to combine development and testing so that it would be easier to achieve software development. So, BI and Dev testing is the right choice for resolving issues related to the BI reports and dashboards.
The client was looking for a way to enhance the portal. The main objective was to display the BI based reports and the dashboard more with the drill down capabilities. Moreover, the client wants to make the reports and dashboards available for all the school districts, municipalities, super pool, hospitals and JPA.
The challenge was overloaded, and it was to be addressed at the earliest. There was a necessity to benchmark the performance of ‘how am I doing?’ reports. One of the significant challenges was changing the current reports so that they could drill down the hierarchy and showcase data and graphs at every level. Moreover, necessary reports are to be framed to use Sales Force structure.
The challenge looked tremendous, so the iterative approach seemed to be the best solution. A BI team was formed, keeping in mind the competency and clear goals. Then the team decided to work with the DWH BI lifecycle and solution model to address the challenges. Moreover, they were set to develop and implement the rich feel of dynamic dashboards to enhance the portal seamlessly.
QA Team Achievements
After the development and implementation stage, the team was set in testing. The aim was to achieve success in the testing, and the team was able to test more than 180+ reports at that time for the systems and integrations. Moreover, testing was also initiated for security and performance for every major release.
Cloud Migration Services for an e-commerce Application
Industry Vertical: Last-mile Delivery
Duration: 6 months
Team Size: 7
Technology: AWS, Python, PostgreSQL
Cloud operations offer a great helping hand in managing cloud operations in a secure way. The operations check on the entire services round the clock to monitor the smooth functioning of the processes. The operations offer services like cloud migration, cloud database migration, application modernisation, cloud architecture services, cloud pilot designing and cloud maintenance. These services take care of the entire migration process of the databases and ensure a complete and structured way of maintaining the cloud infrastructure.
The challenge was pertaining to the field of the last-mile delivery industry. The client is looking for a way to re-architect the PaaS of the AWS cloud platform and the last mile delivery platform through the various services offered for maintaining the cloud system.
The client was posed with a challenge in the cloud platform leading to so many disruptions. Their platform contained multiple services, which were an obstacle that involved various integrations. They faced another major challenge: re-architecting the Platform as a Service (PaaS) and then relocating it to a multi-tenant and cloud platform. This was for the sole purpose of seamlessly managing the performance and cost optimisation.
After careful consideration and analysis, the approach chosen to work on the challenges involved the methodology of iteration. They used tools like AWS, PostgreSQL and Python to handle and work on the platform. Attaining the high availability, they decided to compute the instance optimisation, autoscaling and load balancing. Moreover, they initiated migrating the database to the cloud platform and scaling the policies. The metrics were set down and were constantly checked on its process. They also began to deploy continuously in various environments to manage the system process.
The hustle of the hectic process gave way to a satisfactory and positive outcome. The load balancing seemed to be a little low; however, after the cloud operations, the load balancing managed twenty times peak loads than before, which was a tremendous improvement. Earlier cost optimization was also a hurdle in cloud operation. But, with this process, the cost optimization was computed to 75% from earlier.
The databases were used at an optimal level because of the high availability and security. There were no more delays in the deployment, and it also resulted in zero downtime. Moreover, there was constant tracking and monitoring of the entire platform to ensure that the services were maintained efficiently.