There are several usage patterns for domain-specific languages: ? processing with standalone tools, invoked via direct user operation, often on the command line or from a Makefile (e.g., the GraphViz tool set) ? domain-specific languages which are implemented using programming language macro systems, and which are converted or expanded into a host general purpose language at compile-time or read-time ? embedded (or internal) domain-specific languages, implemented as libraries which exploit the syntax of their host general purpose language or a subset thereof, while adding domain-specific language elements (data types, routines, methods, macros etc.).
published by Anonymous on February 9, 2017 - 16:59
If we talk about automating visual regression testing of web applications, there are some basic features which just cannot be absent in such a tool, that is:
emulate a click,
emulate a text input operation,
compare screenshots retrieved during different runs,
run the recorded test in another browser,
add a new test step etc.
But it's some unique, unusual options which make real difference. Something to do with radically facilitating the regression testing process itself.
Recent comments