From early stages of Webswing development, we felt there is a strong requirement for proper Testing tool to help our customers with creating test cases and with smooth transition to production environment. We’ve created Webswing Test Tool that became integral part of Webswing. However our effort and focus was huge, we’ve been able to incorporate every feature and functionality that we wished for, mainly for very complex test scenarios and large enterprise systems. With many customers of ours, this complexity and matureness of the Test Tool was required.

Back in 2019 we've decided to partner with the global leader for Testing legacy Java applications - QF-Test. QF-Test started with testing Java applications in 2002 and was released for Web testing in 2008. As we are sharing same customer base and QF-Test has already been a ‘way-to-go’ for many of our clients as well, we’ve decided to interconnect our softwares to provide the customers with full scale solution. This brings a great experience on testing these two technologies. QF-Test supports all technologies that Webswing does - like Java swing, JavaFX, Netbeans and Applets.

Integrated testing of Webswing applications with QF-Test is combining two worlds - Webswing brings Java into the web browsers and QF-Test ensures quality through simultaneous interaction with both the Java and the web parts of the applications.

As years pass by, Webswing’s focus shifted strongly towards migration of legacy Java applications into web native technologies. QF-Test also supports these kind of migrations with regression testing. You can write your tests using all data from the legacy Java application which results in highly stable and easy to maintain test cases. Direct usage of those tests in Webswing environment allows you to reuse them in large parts for further migration to native web applications.

See here how well Webswing and QF-Test work together

You can find further information directly on QF-Test page and find out how Webswing testing works with QF-Test, or you can check the technical documentation in our Webswing Docs.


PreviousWebswing Development Vision Updated

NextWebswing 22.1