Closed rutheodora closed 8 years ago
post_question.feature
Feature: Posting a question
Scenario Outline: User post a question
Given user <title> filled the title field
And user <desc> filled the description field
When user click the submit button
Then user is <post> to post a question
Examples:
| title | desc | post |
| has | has | able |
| has | not has | not able |
| has not | has | not able |
| has not | has not | not able |
post_answer.feature
Feature: Posting Answer
Scenario: User wants to answer the question
Given User has filled the answer field
When User clicks the submit button
Then User is able to answer the question
Scenario: User wants to answer the question but not filled the answer field
Given User has not filled the answer field
When User clicks the submit button
Then User is not able to answer the question
list_questions.feature
Feature: List all available questions
Scenario: User is able to see all the available questions
Given Application read the Question database
When User accesses the home page
Then User is able to see all questions
list_questions_answers.feature
Feature: Retrieve Question’s Answer
Scenario: User is able to read the answer of the question
Given App read the Question database and its Answer database
When User clicks the chosen Question box
Then User is able to read the question's answer
@mhaidarh @muhpatr : cek yang ini juga yaw :3
@rutheodora Already checked and modified.
@rutheodora Di atas bahkan udah gue modif the. https://github.com/gunadarma-academy/asde-michi/issues/39#issuecomment-206734132
@mhaidarh ... td belum kerefresh xD
@rutheodora Yowis lo edit semua yang belum.
@rutheodora Checked out and improved. Please pull the latest and close this issue.
SOW
Overview
Create Scenario test for Posting Answer, Posting Question Feature, Retrieve Questions, and Retrieve Question’s answers feature using Gherkin syntax. This test based on some scenario condition for Login and Logout feature.
Tasks
Deliverables
The document will be uploaded to asde-michi-test submodule.
Dependencies
The master test plan needs to be done first (#36 and #37).
Assumptions
This work will be done (for estimated time) before Friday, April 8th, 2016.