The languages (X) HTML, CSS and JavaScript remain the three basic elements of surfaces in Internet - a free program will add more and more XML with XSL style sheets. With most programming languages have this in common that they are not enough highly complex and usually expensive development platform (IDE) need, but a dog usually plain text editor for developing. In a pinch, it goes with "Notepad" - but a bit more comfort to wish you, as a rule anyway. In most programming and markup languages is happy about the following features:
Free search, extraction and replacement with regular expressions, possibility Color highlighting of keywords and comments
discovery of corresponding Brackets, whether square, round or curly
extraction of a kind of Contents - Section specific markers in the document to keep track of documents in large and per-click in a section of branch. In HTML, this is the heading tags
\u0026lt;h1>
, \u0026lt;h2>
, etc., in each JavaScript function
's, in each CSS style rules. An explicitly callable "Pretty Printer" for Spalteneinrückungen - but by no means an automatic!
An explicitly callable "Code Inspector" and syntax check, references to obsolete language elements or critical Codes.
definable key code assignments for commonly used menu items.
Manual callable, user-definable code templates, such as the HTML template - but by no means automatic code generation!
I have to 2003 worked with the editor TextPad , who had some of these features. Later I switched to UltraEdit - because it is commonly used editor in my company.
- For some time, has an attached JavaScript UltraEdit-processor, which offers a more flexible way as macros, recurring transactions, the text editor to automate. There is also a sentence of up to ten user-defined tools - operating system commands that can be applied to the current document. Using a predefined menu can be called even without further adjustment expenses HTML Tidy, a useful "Code Inspector for HTML and XHTML. It can also be used for mere parsing an XML document.
- is for JavaScript code to the Inspector
- http://bsp.mits.ch/supplements/jslint.js . One has to only file in the Script folder pack of UltraEdit and has JSLint then to the script list available. tedious thing, but not impossible, it was a locally running version of the W3C to generate standard CSS validator . The installation is complicated by the fact that the authors have not programmed their tool layer aware - there is no class with which the validator on a text like Input stream can apply, and generates a text-shaped output - but the implementation is as intertwined with the Jigsaw servlet server. Anyone who has a Java Runtime on his computer, can my 7 MB severe folder
JSLint JavaScript veteran Douglas Crockford. It was a natural idea to have this run with the built-in JavaScript UltraEdit processor. This is actually easily possible and also has the advantage that you can filter the output according to their own ideas in order not are flooded with messages, but only show what you yourself consider to be material. Anyone interested can, my version of UltraEdit JSLint downloaded from the website of the GNP practice book under
download that contains all of the start of the CSS validator unfortunately necessary JAR files. After downloading and extracting it is necessary in the batch file
cssv.bat may change the name of the folder and can then configure a tool. I have the css folder as first-level subfolders on my memory stick and write the command, therefore, in the tool configuration as follows:
\\ css \\ cssv file :///% F% n% e The batch file assumes that the command java
can run. If this is not the case with you, you have to be chosen path of java.exe batch file fully qualify, for example, by placing the environment variable% JAVA_HOME% , or, if you do not have this configured by specifying the full path to java.exe . Again, you can control the Java class
FilterValidatorOutput.java
yet how much output you want to get from the validator.
All these efforts are rewarded by the fact that you have the W3C validator for CSS files offline in the text editor is available. Before you post the files you have in order for HTML (with Tidy), CSS (with the W3C validator) and JavaScript (with CrockfordsECMA
JSLint
) the possibility of consistency checks and audits access to critical code points-per-click or by keyboard shortcut.
need to these static tests after checking in the HTML, CSS and JavaScript code added yet dynamic. How to create automated tests for JavaScript, I have already described in this blog: With the lightweight unit testing framework
people can write unit tests for JavaScript code. It is advisable to keep the current test suite and the latest on the release of the shipments into the Q-system to start - more often they start the better. more dynamic tests of course, affect the surface it self will call often in manual mode, the application and test if for example the new button works as expected. With automation to get there ahead anyway. It is useful to have a test mode without having business logic with which each frame of the application with a simple click may be called, where it is supplied with dummy data and displayed. Such a UI or test mode could be implemented in ABAP with a user parameter: instead of "productive" Models return to work in test mode with subclasses of these models, the dummy data. Once
this is possible, you can also protect the surface as a whole with automated testing: Who has a test tool such as QuickTest Professional version, you can now record dialog steps and build expectations in the form of checkpoints.
with standard tools, you can write tests in a dynamic language. With Perl has the component
HTML:: Parser
use to extract, for example, all links from a page or to navigate the DOM - the individual expectations can then test the module
test: Set More
.
for XML and XHTML output dynamic tests are very good to formulate the schema language Schematron . The language is - in contrast to other schema languages such as XSD schema or DTD's - not grammar-based, but based pattern. This makes it convenient to examine individual test expectations for the structure of the document: If the elements are nested in the expected manner? Are there certain substructures, if so, how often? Do the elements, the expected attribute values and text content? The pattern itself is collected in an XML Schematrondokument and can be used with an appropriate implementation of the XML documents to be checked.
The combination of code inspectors and dynamic tests helps to protect the code to be developed and to ensure changes at all levels, that existing functionality not be altered or destroyed.
0 comments:
Post a Comment