Backend testing automates functionality on the server side of an application. This is important for confirming that interdependent or tightly-coupled components are communicating correctly as well as producing and storing data properly. Performing backend tests is critical for finding and fixing bugs early in a project’s development helps to ensure a robust infrastructure.
Backend testing typically involves testing and validating at least one of the following:
intaQt supports communication interfaces that exchange data within backend systems through its extensive collection of Built-ins. These provide out-of-the-box functionality that cover use cases such as database connections, XML matching, programming language-specific content generation and utility functions. The predefined Built-ins functions apply to many contexts and enable writing complex, custom intaQt tests without the need for additional software. As a result, backend testing can be seamlessly integrated into larger intaQt projects, which is useful for projects that test both the frontend and backend.
intaQt Features for Backend Testing
The HTTP Built-ins are primarily used for Request Builder functions (
options) and their available builder methods, as well as HTTP cookies & cookie stores, HTTP clients & client contexts and HTTP RequestConfigBuilder.
SSH and SCP
Secure Shell (SSH) Built-ins facilitate starting SSH actions, such as batch processing, to accomplish multiple tasks in a single session. Additionally, Secure Copy Protocol (SCP) Built-ins can perform activities such as fetching log files for future analysis.
Lightweight Directory Access Protocol (LDAP) Built-ins provide full LDAP functionality within test cases. Available functions include creating new participants in a telecommunications network, debugging and executing queries.
CSV, JSON, XML and YAML
intaQt efficiently processes responses in CSV, JSON, XML and YAML. These Built-ins support the most important data formats for backend testing. Additionally, XML Built-ins enable processing XML strings. Their two main functionalities involve decoding XML into a map and evaluating XPath to string.
E-Mail and PDF
E-mail and PDF Built-ins allow intaQt to send reports via E-mail in HTML and PDF format within test cases. Additionally, the PDF Built-ins can complete PDF forms before sending them as E-mail attachments.
SQL Built-in facilitates direct access to databases within a test case. Supported functions include query execution, result retrieval and performing standard SQL functions.
Matching Built-ins verify large XML files (for example, larger than 1Gb). They stream files rather than building a model of the structure entirely in memory, which prevents memory issues on standard hardware. Matching Built-ins use objects that hold callbacks, called Matchers, to verify a document.
Fuzz Built-ins provide functions for generating random values, including number ranges, date ranges and strings. It is also possible to exclusively generate such values near boundaries.
intaQt Client is used to execute entire intaQt test projects from the command line, and can be integrated into continuous integration (CI) environments like Jenkins and TeamCity. intaQt’s parallel execution functionality enables running and re-running test suites between very short development cycles. intaQt Client also provides configurable features that allow users to:
- Specify how often to retry failed tests.
- Pass parameters to specify ports, configurations or hosts for different projects.
- Upload local project changes to the server before execution.
- Create XML configuration files to create complex test suites with tags.
QiTASC’s integrated development environment provides features that improve your productivity and the quality of your tests:
- Auto-completion, go-to declarations and rename refactoring help you write, find and edit your tests with ease.
- the intaQt Phone Plug-in, which shows a project’s phones in real time and enables interacting with remote phones from within intaQt Studio.
- Error inspections, line markers and notifications help you identify problems with your code as you write it.
- Create templates, in-code documentation, and more!
QiTASC Product Add-ons
Instantly verify test output as an additional quality check. intaQt Verification may be executed online, as an intaQt test case is being executed, or offline, for example, if data are only collected at the end of each day. In both cases, the following functionality is included with intaQt Verification:
- Selectors - These tell intaQt Verification which records to choose. For example, if only voice call tickets should be used.
- Verification Rules - Rules define the type of “checks” that will be performed against the selected records. For example, checking the difference between two properties like amounts of data used, or the difference in a customer’s account balance.
- Special functions for calculating properties and values such as dates, times and numbers within a test case.
ConQlude Reporting Service
Collect, manage and export intaQt test case project data manage defects, which can be accessed by all members of your project’s team. ConQlude automatically uploads all test reports, logs, media attachments and metadata to a centrally-accessible, secure web interface. conQlude provides approval workflow features and can be integrated into most test management systems and defect tracking systems. Our reporting interface ensures that users can remain confident that all test execution details are 100% correct, up-to-date and conform to formats recognized by external project management systems.