|
Question |
Raised by |
Status |
Solution |
|
|
Alford, Ronald Wayne |
Need
Question |
|
|
In the
approach presented in this paper, the inputs to the state generator are (1)
the database schema and (2) user supplied information. Often times, when the
database is being developed/designed, developers also use several approaches
to check and enforce the schema; how useful is the state-generator approach in
this context? Also how scalable is it? |
Bahety, Anand Baldeodas |
Need
Solution |
|
|
In
Figure 2 of the paper, the authors present the general framework for testing
the database applications. Part of the framework is composed of the DB State
and the 4th Component State Validator. It seems
that this validator would need to check the entire
database. Are there any scaling issues here? If yes, how bad are they? What
can be done to amend them? If there are no issues, how does the toolset deal
with scaling? |
Bucatanschi, Dan George |
Need
Solution |
|
|
Explain
Slide 14 with respect to Slide 17 |
Chandra, Deepti Jagdish |
Need
Solution |
|
|
The
tool seems not explore "difficult" test cases: instead it relies on
user-specified probabilities on some special values. Does that make the 2nd,
3rd,... test cases much less interesting if we have
resources to generate more instances of data? |
Huynh, Thuan Quang |
Need
Solution |
|
|
|
Nguyen, Bao Ngoc |
Need
Question |
|
|
What
are the problems which arise when the Database state is ignored while testing
a database application? |
Konda, Shravya Reddy |
Need
Solution |
|
|
One of the
important issues in testing databases is the role of the database state.
Discuss three possible approaches to dealing with this. |
Lee, Joonghoon |
Need
Solution |
|
|
|
Liu, Liping |
|
|
|
Is it possible
to use this method with large scale database applications? Are there any
issues with scalability? |
Wongsuphasawat, Krist |
Need
Solution |
|
|
Generating
synthetic databases is not as straightforward as generating random values for
every attribute in the DB. Why not? |
Reisner, Elnatan
Benjamin |
Need
Solution |
|
|
|
Schulman, Aaron David |
Need
Question |
|
|
What
are the possible approaches for dealing with the role of DB state in testing?
What are the problems that can arise, if any? Explain. |
Sharara, Hossam Samy Elsai |
Need
Solution |
|
|
The
tool architecture proposed by the authors does not seem to test for
concurrency. Is their architecture adequate, or could it be modified to test
situations where several users are modifying the data simultaneously? |
Stuckman, Jeff |
Need
Solution |
|
|
|
Teoh, Alison Lui Koon |
Need
Question |
|
|
The
approach in the paper measures adequacy with respect to the specifications of
the database, the program and heuristics. Can this approach be used for
automated test data generation, or is tester intervention always required? |
Thakor, Shashvat Advait |
Need
Solution |
|
|
|
Vador, Sachin Shashikant |
Need
Question |
|
|
|
Donlon, Eileen Merle |
Need
Question |
|
|
When
testing database applications not only the internal state of the program has
to be considered but also the data that is preexisting, read and written into
the database (state of the database). What problems can arise when filling
the database with artificial data before starting the application? |
Zazworka, Nico |
Need
Solution |
|