White stem borer damage and grain yield in irrigated rice in West Java, Indonesia

Factors influencing the relationship between whiteheads caused by the white stem borer Scirpophaga innotata (Walker) and grain yield were investigated. We determined the effect of different numbers of whiteheads on grain yield using different cultivars, nitrogen application, and at different field locations in Cilamaya, West Java. At the same number of panicles and whiteheads per plant, yield reduction is greater in cisadane than in IR64. With increasing nitrogen application, the range in panicle height increased. Except for Ketan, more whiteheads were recorded in shorter panicles. Two locations planted to the same cultivar showed different relationships between whiteheads and grain yield. The relationship between whiteheads and grain yield depends on the distribution of whiteheads in the field. Unless these factors have been taken into consideration, it may be difficult to make a damage prediction of white stem borer in the field. (C) 1997 Published by Elsevier Science Ltd.

A framework for table driven testing of Java classes

With the advent of object-oriented languages and the portability of Java, the development and use of class libraries has become widespread. Effective class reuse depends on class reliability which in turn depends on thorough testing. This paper describes a class testing approach based on modeling each test case with a tuple and then generating large numbers of tuples to thoroughly cover an input space with many interesting combinations of values. The testing approach is supported by the Roast framework for the testing of Java classes. Roast provides automated tuple generation based on boundary values, unit operations that support driver standardization, and test case templates used for code generation. Roast produces thorough, compact test drivers with low development and maintenance cost. The framework and tool support are illustrated on a number of non-trivial classes, including a graphical user interface policy manager. Quantitative results are presented to substantiate the practicality and effectiveness of the approach. Copyright (C) 2002 John Wiley Sons, Ltd.

Chloroquine or sulfadoxine-pyrimethamine for the treatment of uncomplicated, Plasmodium falciparum malaria during an epidemic in Central Java, Indonesia

A recent malaria epidemic in the Menoreh Hills of Central Java has increased concern about the re-emergence of endemic malaria on Java, which threatens the island's 120 million residents. A 28-day, in-vivo test of the efficacy of treatment of malaria with antimalarial drugs was conducted among 16 7 villagers in the Menoreh Hills. The treatments investigated, chloroquine (CQ) and sulfadoxine pyrimethamine (SP), constitute, respectively, the first- and second-line treatments for uncomplicated malaria in Indonesia. The prevalence of malaria among 1389 residents screened prior to enrollment was 33%. Treatment outcomes were assessed by microscopical diagnoses, PCR-based confirmation of the diagnoses, measurement of the whole-blood concentrations of CQ and desethylchloroquine (DCQ), and identification of the Plasmodium falciparum genotypes. The 28-day cumulative incidences of therapeutic failure for CQ and SP were, respectively, 47% (N = 36) and 22% (N = 50) in the treatment of P. falciparum, and 18% (N = 77) and 67% (N = 6) in the treatment of P. vivax. Chloroquine was thus an ineffective therapy for P. falciparum malaria, and the presence of CQ-resistant P. vivax and SP-resistant P. falciparum will further compromise efforts to control resurgent malaria on Java.

Movements of the ricefield rat, Rattus argentiventer, near a trap-barrier system in rice crops in West Java, Indonesia

The movements of the ricefield rats (Rattus argentiventer) near a trap-barrier system (TBS) were assessed in lowland flood-irrigated rice crops in West Java, Indonesia, to test the hypothesis that a TBS with a 'trap-crop' modifies the movements of rats within 200 m from the trap-crop. The home range use and locations of rat burrows were assessed using radiotelemetry at two sites, one with a TBS with trap-crop (Treatment site, the crop inside the fence was planted 3 weeks earlier than the surrounding crop) and the other with a TBS without trap-crop (Control site, the crop inside the fence was planted at the same time as the surrounding crop). Each TBS was a 50 x 50 m plastic fence with eight multiple-capture rat traps set at the base. More than 700 rats were caught in the TBS with trap-crop, whereas only 10 rats were caught in the TBS without trap-crop. The home range size of females was significantly smaller at the Treatment site (0.96 ha) than the Control site (2.99 ha), but there was no difference for males. Seventy-eight per cent of rats caught in the TBS and fitted with radiocollars had their daytime burrow locations within 200 m of the TBS. We could not determine if the rats caught in the TBS were residents or transients according to demographic parameters. Our results support the hypothesis that a TBS with a trap-crop protects the surrounding rice crop out to a distance of at least 200 m.

Tool support for testing concurrent Java components

Concurrent programs are hard to test due to the inherent nondeterminism. This paper presents a method and tool support for testing concurrent Java components. Too[ support is offered through ConAn (Concurrency Analyser), a too] for generating drivers for unit testing Java classes that are used in a multithreaded context. To obtain adequate controllability over the interactions between Java threads, the generated driver contains threads that are synchronized by a clock. The driver automatically executes the calls in the test sequence in the prescribed order and compares the outputs against the expected outputs specified in the test sequence. The method and tool are illustrated in detail on an asymmetric producer-consumer monitor. Their application to testing over 20 concurrent components, a number of which are sourced from industry and were found to contain faults, is presented and discussed.

Tool support for executable documentation of Java class hierarchies

While object-oriented programming offers great solutions for today's software developers, this success has created difficult problems in class documentation and testing. In Java, two tools provide assistance: Javadoc allows class interface documentation to be embedded as code comments and JUnit supports unit testing by providing assert constructs and a test framework. This paper describes JUnitDoc, an integration of Javadoc and JUnit, which provides better support for class documentation and testing. With JUnitDoc, test cases are embedded in Javadoc comments and used as both examples for documentation and test cases for quality assurance. JUnitDoc extracts the test cases for use in HTML files serving as class documentation and in JUnit drivers for class testing. To address the difficult problem of testing inheritance hierarchies, JUnitDoc provides a novel solution in the form of a parallel test hierarchy. A small controlled experiment compares the readability of JUnitDoc documentation to formal documentation written in Object-Z. Copyright (c) 2005 John Wiley & Sons, Ltd.

Mutation-based exploration of a method for verifying concurrent Java components

Summary form only given. The Java programming language supports concurrency. Concurrent programs are harder to verify than their sequential counterparts due to their inherent nondeterminism and a number of specific concurrency problems such as interference and deadlock. In previous work, we proposed a method for verifying concurrent Java components based on a mix of code inspection, static analysis tools, and the ConAn testing tool. The method was derived from an analysis of concurrency failures in Java components, but was not applied in practice. In this paper, we explore the method by applying it to an implementation of the well-known readers-writers problem and a number of mutants of that implementation. We only apply it to a single, well-known example, and so we do not attempt to draw any general conclusions about the applicability or effectiveness of the method. However, the exploration does point out several strengths and weaknesses in the method, which enable us to fine-tune the method before we carry out a more formal evaluation on other, more realistic components.

Testing java interrupts and timed waits

Testing concurrent software is difficult due to problems with inherent nondeterminism. In previous work, we have presented a method and tool support for the testing of concurrent Java components. In this paper, we extend that work by presenting and discussing techniques for testing Java thread interrupts and timed waits. Testing thread interrupts is important because every Java component that calls wait must have code dealing with these interrupts. For a component that uses interrupts and timed waits to provide its basic functionality, the ability to test these features is clearly even more important. We discuss the application of the techniques and tool support to one such component, which is a nontrivial implementation of the readers-writers problem.