One of the key enhancements in v5.1 of Spira is the use of SQL Server free text indexing to provide a completely new search experience. The new search capabilities in Spira 5.1 are a dramatic improvement over the previous version.
The move to cloud computing has highlighted the importance of
Application Programming Interfaces (APIs). With the rise in cloud
applications and interconnect platforms, API testing is a necessity. However what makes a good API? What happens when you change the application but need to support existing users of the API?
I have had the pleasure this week of attending the Microsoft Dynamics 2016 Summit in sunny Tampa, Florida. We have several customers of ours beta testing the new functionality in Rapise 5.0 that makes testing Dynamics AX and CRM rapid and easy. Microsoft has some big changes planned for Dynamics and we're looking forward to helping you test your systems as you make the transition.
In an ideal world, the presentation layer would be very simple and with
sufficient unit tests and other code-level tests (e.g. API testing if
there are external application program interfaces (APIs)) you would have
complete code coverage by just testing the business and data layers.
Unfortunately, reality is never quite that simple and you often will
need to test the Graphic User Interface (GUI) to cover all of the
functionality and have complete test coverage.
I had an interesting discussion with a prospective client last week - they were using another planning tool (Microsoft TFS) and were looking for a tool that would give them a more structured process, but had an easier to use, less painful UI.