FitNesse vs. ignio AIOps

Useful and straightforward. Appian and other low-code BCM tools can be easily integrated. Writing a script for a test is similar to writing a script in English. So simple to use because it's a wrapper class for selenium. FitNesse is being implemented with the goal of doing it correctly the first time. As a result, migrations of both the client and the server are made easier.

Incentivized

It's good for issue resolution, user access request automation, standard report generation, health checks, executing self-healing as configured in the attributes. Currently not good at real-time monitoring to trigger an action. Health checks have to be on a scheduled basis.

• Easy to install.
• Command language is easy to create custom scripts.
• FitNesse tests are deterministic.

Incentivized

• ignio handles 100+ use cases covering the entire organization including applications and infrastructure.
• Centralize the dashboard to view and executed the health of systems in our environment.
• It handles CA services desk Incidents and requests. Using automated tools with power shell scripts.
• ignio event management helps the organization to manage the alerts well and make an informed decision.

• Logging can help any debug or error issues.
• A Java/Selenium developer is needed to maintain the FitNesse keyword library.
• Content.txt and properties.txted need to be added to the test suite in older versions to make it visible in a test run.

Incentivized

• There is a lot more the desktop tool can do. For example, we need to apply an upgrade to get the tool to talk to our infrastructure while employees are working from home. The tool was initially installed with the assumption that the desktops would be in UserLand. Instead after COVID-19 the desktop/laptops have been used for over a year on people's home networks. As of right now, we have to sync when the devices are connected to VPN. Moving forward with the upgrade, we will be getting this data over TLS when they are connected to the untrusted networks.
• The concept of ignio AlOps requires OCM efforts within most operational teams. This isn't necessarily the fault of the tool itself, but when implementing ignio, or any AIOps tool, the team will get a lot of pushback as an outside team is centralizing the operational improvements. The tool should have a centralized intake process that will allow the collection, ranking, and management of automation opportunities. ignio AlOps should then simulate the proposed efficiencies from implementing something within the backlog. Right now a lot of local teams are having a hard time getting on the same page as the enterprise teams, and a common methodology for prioritizing (even if overly simplistic) would go a long way to enterprise planning.
• These tools are very new and things get added to them all the time. There should be a way for the product's stakeholders and process owners to understand the additional value ignio AlOps is gaining over time.

It is a very good product and it helps our organization.

ignio AIOps version upgrades were a heavy lift. Having to learn a new language versus an industry standard language took time. More consideration on overall internal long-term support needs to be determined.

Incentivized

It was up than Dynatrace

Incentivized

We had performance issues in older version butterfly. But the new version cheetah is simply amazing

We have built a healthy relationship with the vendor support team throughout the implementation phase, all incidents raised were resolved within the SLA without a fail

Implementation team has provided necessary training & enablement.

Online training materials are shared by the implementation team and it was good.

I am happy with the way team has implemented and shared the product for our organization. However, would like to see it get extended to the other line of business too.

The FitNesse testing automation framework is very simple to operate. It is simple to connect with the Jenkins and Bamboo environments. It is dependable, and it is simple and quick to include new tests. The process of debugging and fixing test failures is straightforward. FitNesse, including its installation, may be utilized with a minimum of fuss and difficulty. Maintaining scripts and monitoring their output is designed to be a relatively straightforward process.

Incentivized

Self HEAL OOB Capabilites

Quite Scalable!

• It does not necessitate any further setup or configuration.
• FitNess is an easy-to-use manual QA tool with a comprehensive report that aids stakeholders in better understanding the tested applications.
• Automated testing suites for a wide range of websites. In addition, it is quite beneficial for the ongoing maintenance of the test library.

Incentivized

• ignio has had a positive impact on our organization by saving 7,000+ hours within Operations and automatically resolving 84% of our service requests.
• ignio has increased our alert coverage by over 60%.