Testing Enterprise Software Rewrites
Most enterprises have legacy code that needs to be rewritten to keep pace with industry standards, new technologies, and modern infrastructures. The primary purpose of an enterprise software rewrite is to ensure functional compatibility before retiring a legacy system. However, replacing large, complex, bread-and-butter legacy systems is a risky and costly project endeavor, frequently resulting in projects failing, being shelved, or abandoned. Software rewrites face significant challenges due to detailed code requirements, legacy infrastructure, and lack of support. Umang Nahata discusses test strategies and assessments he has used to resolve these challenges. Explore techniques, practices, and lessons learned to effectively manage and test software rewrites. Hear Umang’s experience on minimizing software architectural transformation for effective delivery and scoping, auditing test data for internal systems, using legacy systems as test oracles, and building effective automation. Join Umang as he shares real-life examples of successful software rewrites and take away a valuable perspective to deliver software rewrites in your organization.
Umang Nahata is a senior system test engineer with Progressive Insurance, where he applies architectural, technical, and process knowledge to deliver software assets that add value by increasing the breadth, coverage, and speed of testing. He has an inquisitive spirit and researches new approaches, tools, and techniques to solve complex testing problems. A software developer at heart with a passion for building quality software, Umang has a talent for creating effective test strategies. He has been in the IT industry for more than ten years in a variety of roles and experiences. Umang is passionate about software testing, test automation, and advocating better collaboration for building better software.