B

backwards compatible
base class
  implementation
  table of components
batchtest
Bean Scripting Framework, Ajax
BeanUtils
beginXXX
best practices
  always specify a reason for skipping a test
  always verify that the test fails when it should fail
  assertions helper
  choose meaningful test method names
  continuous regression testing
  create complementary tests
  database testing
  database tests
  don’t hardcode values
  don’t write business locic in mock objects
  EasyMock object creation
  explain the failure reason in assert calls
  JSLint
  let the test improve the code, 2^nd
  make exception tests easy to read
  make sure target database is tested
  one database per developer
  one unit test equals one @Test method
  plan your dataset usage
  refactor
  same package, separate directories
  test anything that could possibly fail
  test cleanup
  test only what can possibly break
  throw an exception for methods that aren’t implemented
  unit test one object at a time
  use TDD XP principles
  when writing load test cases
  write failing tests first
black box testing
  approaches
  combining with white box testing
  coverage
  JSF
  vs. white box
bootstrappers
branches
browserbot
browsers
  Ajax testing challenges
BSF.
    See Bean Scripting Framework.
build descriptor, namespaces
build file
  Ant
  properties
build lifecycles
build phases
build.dir
build.xml
  cactifyear
  cactifywar
  Cactus
buildresultsurl
BundleActivator
BundleContext
BundleID
business layer
  interface
  testing
  unit testing