Automated test case generation for programs specified by relational algebra queries

Tsai, Wei‐Tek; Volovik, D.; Keefe, T.F.

doi:10.1109/32.48939

Cited by 51 publications

(18 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the literature Tsai et al [6], introduced mutants by changing a set of mathematical operators in the code to determine the fault detection ability of the test cases. In testing database transitions with AGENDA, Chays and Deng injected faults in queries as a final step to demonstrate the adequacy of their proposed approach [7].…”

Section: B Mutation Testing For Database Applicationsmentioning

confidence: 99%

Applying Genetic Algorithms to Test JUH DBs Exceptions

Alshraideh¹,

Jawabreh²,

Mahafzah³

et al. 2013

IJACSA

View full text Add to dashboard Cite

Abstract-Database represents an essential part of software applications. Many organizations use database as a repository for large amount of current and historical information. With this context testing database applications is a key issue that deserves attention. SQL Exception handling mechanism can increase the reliability of the system and improve the robustness of the software. But the exception handling code that is used to respond to exceptional conditions tends to be the source of the systems failure. It is difficult to test the exception handling by traditional methods. This paper presents a new technique that combines mutation testing and global optimization based search algorithm to test exceptions code in Jordan University Hospital (JUH) database application. Thus, using mutation testing to speed the raising of exception and global optimization technique in order to automatically generate test cases, we used fitness function depends on range of data related to each query. We try to achieve the coverage of three types of PL/SQL exceptions, which are No_Data_Found (NDF), Too_Many_Rows (TMR) and Others exceptions. The results show that TMR exception is not always covered this due to existence of primary key in the query, also uncovered status appear in nested exceptions.

show abstract

Section: B Mutation Testing For Database Applicationsmentioning

confidence: 99%

Applying Genetic Algorithms to Test JUH DBs Exceptions

Alshraideh¹,

Jawabreh²,

Mahafzah³

et al. 2013

IJACSA

View full text Add to dashboard Cite

show abstract

“…Tsai et al [49] translate the query into a set of systems of linear inequalities. Zang et al [50] and Khalek et al [51] generate a set of constraints that feed a general purpose constraint solver.…”

Section: Related Workmentioning

confidence: 99%

Full predicate coverage for testing SQL database queries

Tuya

Suárez-Cabal

Riva

2010

Software Testing Verif & Rel

View full text Add to dashboard Cite

SUMMARYIn the field of database applications a considerable part of the business logic is implemented using a semi-declarative language: the Structured Query Language (SQL). Because of the different semantics of SQL compared to other procedural languages, the conventional coverage criteria for testing are not directly applicable. This paper presents a criterion specifically tailored for SQL queries (SQLFpc). It is based on Masking Modified Condition Decision Coverage (MCDC) or Full Predicate Coverage and takes into account a wide range of the syntax and semantics of SQL, including selection, joining, grouping, aggregations, subqueries, case expressions and null values. The criterion assesses the coverage of the test data in relation to the query that is executed and it is expressed as a set of rules that are automatically generated and efficiently evaluated against a test database. The use of the criterion is illustrated in a case study which includes complex queries.

show abstract

“…The current research literature reports on specific tools for specific formal specification languages [9,12,27,34,47,53,55], manual methods for deriving tests from specifications [2,3,8,22,28], case studies on using specifications to check the output of the software on specifications [23,36,39,50], and formalizations of test specifications [7,16,52,51]. The term specification-based testing is used in the narrow sense of using specifications as a basis for deciding what tests to run on software.…”

Section: Related Workmentioning

confidence: 99%