Feedback-Based Specification, Coding and Testing with JWalk

Simons, Anthony J. H.; Griffiths, Noola; Thomson, C. J.

doi:10.1109/taic-part.2008.20

Cited by 2 publications

(7 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Our previous experiments have shown that trying to achieve similar complete test coverage by manual test case selection will yield much poorer results [2,21]. The JWalk tools take control of the selection of test cases, here guided by algebraic analysis, relieving the tester of this burden.…”

Section: Discussionmentioning

confidence: 99%

“…Specification-based testing methods seek to validate the software unit completely against a formal specification, which serves as a test oracle. Recently, these approaches have started to converge, particularly in the lazy systematic unit testing method [1,2], which combines semi-automatic inference of the test unit's specification with systematic conformance testing from the specification. The power of this method depends critically on an automated dynamic analysis to identify the most important test cases, whose outcomes must be confirmed by the tester.…”

Section: Overviewmentioning

confidence: 99%

“…The current work relates to the latest version of the JWalk tool suite, which comprises a number of tools, including JWalkTester, a GUI-based testing tool in the spirit of JUnit [13], JWalkUtility, a command-line version that prints all results to standard output, and JWalkEditor [2], an integrated Java editor, compiler and testing tool, with Java-sensitive syntax highlighting in the style of jEdit [14]. All of these incorporate the common JWalker test engine, which is also offered as a component toolkit API for integration with other editors or testing tools.…”

Section: The Jwalk Family Of Testing Toolsmentioning

confidence: 99%

“…Lazy specification refers to a delayed approach to software specification, in which the specification evolves rapidly in parallel with frequently modified code [2]. The specification is inferred by a semi-automatic analysis of a prototype software unit, with some user-interaction.…”

Section: The Jwalk Family Of Testing Toolsmentioning

confidence: 99%

“…In the validate-modality, the tool also interacts in a limited way with the tester, who must confirm or reject certain key test outcomes, which are compiled in an oracle and used to predict further test outcomes. Eventually, over 90% of testing is fully automated using saved, or predicted outcomes [1,2].…”

Section: The Jwalk Family Of Testing Toolsmentioning

confidence: 99%

See 4 more Smart Citations

Dynamic Analysis of Algebraic Structure to Optimize Test Generation and Test Case Selection

Simons

Zhao

2009

2009 Testing: Academic and Industrial Conference - Practice and Research Techniques

Self Cite

View full text Add to dashboard Cite

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Overviewmentioning

confidence: 99%

Section: The Jwalk Family Of Testing Toolsmentioning

confidence: 99%

Section: The Jwalk Family Of Testing Toolsmentioning

confidence: 99%

Section: The Jwalk Family Of Testing Toolsmentioning

confidence: 99%

See 3 more Smart Citations

Dynamic Analysis of Algebraic Structure to Optimize Test Generation and Test Case Selection

Simons

Zhao

2009

2009 Testing: Academic and Industrial Conference - Practice and Research Techniques

Self Cite

View full text Add to dashboard Cite

show abstract

Reducing user input validation code in web applications using Pex extension

Frajták

Bureš

Jelínek

2014

Proceedings of the 15th International Conference on Computer Systems and Technologies

View full text Add to dashboard Cite

Validation of user input data is very important in web application. Not only it protects the system from various exploits, but it also improves the user experience. User immediately sees what values are missing or are not valid and should be fixed. It is important to validate code on client side in the browser, but that does not mean that the validation on server side can be omitted. The golden rule of the web applications is not to trust user input and validate code on server side as well. The user input validation is therefore duplicated -it validates the input values first on client side using JavaScript before the data is sent to server and then the received data is validated again on the server side. Changes made to the validation code must be synchronized in code on both sides. All implementations must be also unit tested, multiple sets of unit tests must be created and maintained. We will describe how we extended white-box testing tool Pex to generate user input validation code for web applications created on .NET platform. The JavaScript client side validation code is generated from the controller code written in C#. The code then validates input values on the client side. Most of the testing can be automated executing generated test. Testing resources -i.e time spent on testing and number of testers involved people -are saved.

show abstract

Feedback-Based Specification, Coding and Testing with JWalk

Abstract: JWalk is a lazy systematic unit-testing tool for

Cited by 2 publications

References 6 publications

Dynamic Analysis of Algebraic Structure to Optimize Test Generation and Test Case Selection

Dynamic Analysis of Algebraic Structure to Optimize Test Generation and Test Case Selection

Reducing user input validation code in web applications using Pex extension

Contact Info

Product

Resources

About