FormalTestingofWebContentusingTTCN–3.ppt

Formal Testing of Web Content using TTCN-3 By Robert Probert, Bernard Stepien, Pulei Xiong University of Ottawa Motivation Web Applications (WA) are the most widespread target domain of software development in computer history. WA are error prone because mostly because anyone can develop them and they are mostly distributed. Testing of WAs: manual or using dedicated tools or robots. Current state of researchon formal Web content testing XML based formalism Xiaoping Jia and Hongmin Liu, Rigorous and Automatic Testing of Web Applications Sahil Thaker, Robust Testing for Web Applications Web content testing elements Hyperlink checking, including recursive Text fragment checking Protocol checking Table checking Form checking Formatting checking Mirror sites content checking Version checking (languages,etc…) Invalid HTML syntax checking … Specific needs of web content testing TTCN has been originally designed for telecommunication protocols. In Telecom, every single data element is relevant and needs to be coded and decoded to and from the abstract layer. In Web application, only part of the content is testable and needs to be extracted because most of the web page content is either too large or unpredictable. Thus, in web content testing, we test only invariants. DePaul U Formalism BNF Text Fragment checkingDePaul U formalism Mapping DePaul U Formalism to TTCN-3 Testsuite - testsuite Testcase - testcase Teststep - function Request - send Response - receive Match - built-in TTCN-3 matching mech. Regexp - pattern Value - template Text Fragment checking TTCN-3types and templates Text Fragment checking TTCN-3test case Text Fragment checking TTCN-3test logic Contains concept and TTCN-3 pattern The ‘and’ operator does not imply sequence. Permutations of values must be specified in the TTCN-3 template using pattern. Combinatorics explosion when the number of text fragments increases (np). TTCN-3 should implement a concept of “contains” with logical expressions Evaluat