As a possible solution:
You can add BDD solution to your test framework. For Java popular BDD solutions are JBehave and Cucumber-JVM. So other members will write tests in Gherkin human-like language.
How it looks like? — you may ask..
The test it self is a textual description:
Feature: Adding
Scenario: Add two numbers
Given the input "2+2"
When the calculator is run
Then the output should be "4"
Gherkin notation is used here which is:
Given [context] — When (I do) [action] — Then (I should see) outcome
Steps are implemented in programming language:
Given /^the input "([^"]*)"$/ do |input|
@input = input
end
When /^the calculator is run$/ do
@output = `ruby calc.rb #{@input}` raise('Command failed!') unless $?.success?
end
Then /^the output should be "([^"]*)"$/ do |expected_output|
@output.should == expected_output
end
Often human-like stories are developed by manual testers
and then they're partially or fully automated by automation engineers.