KeyFruit Corporate Website

A beta tester is someone who tests a product before it is released; that’s us
Product testers help companies identify weak points in their products which could cause consumer frustration, and they also identify specific issues which need to be corrected before a product can be released. Typically, beta testers test several incarnations of a product, until it is deemed ready for release. Most commonly, beta testers work with electronics and software. Our expertise is in web site beta testing.
Let’s assume that your company’s product is your new corporate web site, or again your new 1 million dollar sell-out sales campaign micro site. Who tests it? What are test methodologies conducted? By whom and how are the errors or bugs reported?

KeyFruit applies two different testing methodologies for a scenario like above;

Black box testing

This is where we treat your online product as a “black box”—without any knowledge of internal implementation. Black box testing methods include: equivalence partitioning, boundary value analysis, all-pairs testing, fuzz testing, model-based testing, traceability matrix, exploratory testing and specification-based testing.

White box testing

White box testing is when the tester has access to the internal data structures and algorithms including the code that is implemented. KeyFruit’s white box testing methodology includes:

• API testing (application programming interface) – Testing of the application using Public and Private APIs

• Code coverage – creating tests to satisfy some criteria of code coverage (e.g., the test designer can create tests to cause all statements in the program to be executed at least once)

• Fault injection methods

• Mutation testing methods

• Static testing – White box testing includes all static testing

Beta testing can be taken as the life insurance of your online products. You can never know when you’ll need it.