Test Driven Development (TDD) is a method of software development that uses testing for certain functionality to reduce the amount of code that needs to be written. Using TDD techniques, software testers (or developers themselves) write specific tests for certain functionality in the software being developed, and then run these automated tests to determine if the code passes or fails. New code is only written for those functions that fail the tests, speeding up the development process and shortening time to market.
Stress testing is a type of performance testing designed to test the endurance, robustness or stability of an application, system or network. Testers are generally more interested in defects and anomalies caused by system failures from stress testing, rather than the failures themselves (which are expected).
Quality Assurance (QAT) is a subset of the SQA process that uses metrics to determine the overall quality of a software product, from development through to user experience. QAT ensures the optimal testing methodologies, feedback loops and development processes are used for the required product deliverables.
NetDocuments is synonymous with document management in the legal industry, but as with many other document management systems (DMS) it poses several challenges for the software testers tasked with keeping it optimised.
If you’re planning your firm’s next software deployment, be it a document management system like NetDocuments or a practice management system like Elite 3E, then you’re going to want to ensure it installs, integrates and performs optimally.
Thomson Reuters 3E is a complex application with simple interfaces. There are countless screens and endpoints to test which makes it arduous to get full coverage through manual processes. The first thought that any Quality Assurance specialist will have is - can we automate this?
Test Automation is the process of using test scripts to automatically interrogate various software and system functions to ensure they work as expected. While Test Automation has many benefits over Manual (or Functional) Testing, it is best used in conjunction with Manual and Exploratory Testing for the most comprehensive Quality Assurance possible.
If you’ve already tested something at the Unit level, and again at the API level, testing it again at the UI level is just a redundancy that’s going to waste your time, so you need to identify: