Discover more from neeto blog
neetoTestify got bulk updates, duplicate steps, ancestry gem, formikEditor and more
neetoTestify is a test management software to help you manage test cases and test runs. Here are some of the new features, enhancements, and optimizations which were recently launched.
1. Bulk Update Milestone
One of the most significant additions is the ability to bulk update milestones. This feature makes it easy to update the milestone for multiple test cases simultaneously, saving time and reducing the chance of errors.
2. Bulk delete suites and test cases
Similarly, we've added the ability to bulk delete test suites and test cases.
3. Duplicating a step
We've added the ability to duplicate a step. This feature makes it easy to create new test case step based on existing ones. This was a highly requested feature from our QA team and would be helpful to others using neetoTestify as well.
4. Better usage of ancestry gem
This is one of the performance optimizations we made related to using the ancestry gem. Ancestry is a ruby gem used to manage hierarchical data structures in Active Record. Initially, we were not using the gem to its full potential, but after thoroughly reviewing the documentation, we've implemented several techniques to optimize its usage.
the .arrange method for easy and optimized data retrieval.
using materialized_path2 for faster descendent queries
Using collation for indexing the database queries.
These changes have significantly improved the speed and performance of neetoTestify, especially when dealing with large data numbers of nested suites and test cases. We are working on a more extensive blog to cover the optimization details. That blog should be published shortly.
5. Refactored code to better manage steps
Initially, test case steps and run case steps were separate entities. We've now combined both into one step as a polymorphic association to make it easier to manage and maintain test cases. This change has simplified the codebase and made it easier to debug issues related to test case steps.
6. Separate endpoint for fetching options for dropdowns
We have created a separate endpoint for fetching options for dropdowns in forms. This has improved the page-load speed by reducing the number of unnecessary API calls, especially when a lot of unnecessary information was being fetched via the common API endpoints.
7. Used FastField in FormikEditor
We've replaced the Field component with FastField in FormikEditor - part of neetoEditor, which has significantly improved the performance of neetoEditor. This change would also improve the editor performance of all neeto products.
8. Reduced the number of re-renders for forms
Using debounce logic, we added a delay to Formik validation in the test case edit page. This change has reduced the number of unnecessary rerenders and improved performance, especially when dealing with large forms.
Subscribe to this neeto blog to see what we are up to. We'll spill the beans on our out-of-this-world marketing maneuvers (we write blogs like this one). Prepare to have your jaw hit the floor as we reveal revenue numbers that make Elon Musk jealous(we might need a few more zeroes to reach "buy-an-island" status).
And when it comes to reeling in new customers, we've mastered the art of hypnotizing business folks with our mesmerizing PowerPoint presentations that make them chant "neeto!" while doing the Macarena. So buckle up, my daring friend, and hop on board the neeto rollercoaster of insanity!
Warning: Side effects may include an irrepressible desire to shout "neeto!" from the highest rooftops.Welcome to the land of outrageousness, where the mundane is banished and extraordinary reigns supreme! Let the absurdity begin as we embark on a mission to leave our mark on the world, one glorious dent at a time.