adessocucumber/cucumber

This project aims to achieve wholistic platform for BDD scenario creation to automated testing.

cucumber's Issues

Fix creation of multiple scenarios

Creating a scenario does add more than 1 scenario to the database.

Visual test response

As a user,
I want a visual response of my scenarios
So I can see if a test passed or failed

Test Case

This is a Test

APIs don´t work

following APIs doesn´t work:
/api/scenario/add/:issueID
/api/scenario
/api/scenario/:id

CoP2 Vortrag

Login to the website

Seed-Test

Test the our own website

Test für den Summit2019 !!

balbla

Logout scenario

As a user,
In order to validate authentication,
I want a logout option
To test my logout

Sent Notification for feedback and starting up the repo

Sent Notification for feedback and starting up the repo to the designated persons.

Oberflächen Test

Test all buttons

Transfer Github repo to Organisation

Transfer the Github repo to the account of the organisation

Deploy backend application (Prototype 1)

Deploy backend application on Heroku

Alpha Testing

Welcome Tester! Please write your scenarios in this story.

"Authorization Header" for deploy

For the deployed version of the backend app we need to use an authorization key to prevent usage of other apps etc. of the API.

https://www.npmjs.com/package/acl

add Scenario number is wrong

Adding a new scenario creates the highest number in the "name". Just delete the added number in "name".

Transfer Source Code to Github

Transfer the source code to Github on 24.12

Story creation

As a user,
I want to be able to create new features
So I can test features of my project

Implement API functionality

GET: /api/stories; /api/stepDefinitions
POST: /api/scenario/update/:issueID (expects full 'scenario' as json)
POST: /api/scenario/add/:issueID; /api/scenario/delete/:issueID (expects full 'scenario' as json)

CoP Vortrag

This is a Test

add selection on given.role in test data

The selection for the given.role are defined in the step definitions ["Guest", "User"].
The selection is also needed in the stories test data!

CoP Test

Login Test

Sign-Up scenario

As a user,
In order to validate authentication,
I want a sign up option
To test signing up new users

Login scenario

As a user,
In order to validate authentication,
I want a login option with username and password
To test my login

Stepdefinition: set Id

when adding a step type: delete the stepType
add an Id

"Test Data" transfer

Transfer the created scenarios into the test data (backend) after this issue is completed:
#14

/api/stories shows not only stories

The "/api/stories" delivers all issues not only issues labeled with "stories".

Change "/api/scenario/delete/:scenarioID"

Change the "/api/scenario/delete/:scenarioID" to "/api/story/:storyID/scenario/delete/:scenarioID".
See: https://blog.angular-university.io/angular-http/

Implement frontend application

Implement database (backend) functionality

Implement database functionality like write, read, update etc.

New Issue for Testing

this issue tests the workflow of the cucumber app

Scenario creation

As a user
In order to create different testcases
I want to add a scenario to story
when there are stories available.

Access scenario

As a user,
In order to validate authentication,
I want an access option
To test accessing websites

Display Assignee

Display the assignee name ( story["assignee"] )
and the Avatar ( story["assignee_avatar_url"] )
next to the Story Name

Create scenarios for each story

Create for each assigned story 3 different scenarios.

Fix Bug: adding new Scenario to an empty story

adding new Scenario to an empty story causes:

• saveButton disappers (in the whole App)
• new Scenario is not Named
• multiple scenarios are created after reload

Rename scenarios

As a user,
I want to rename scenarios
So I can rectify mistakes in scenario titles

Cannot save new scenario or change scenario

If I try to change a scenario step e. g. the website url and save, it doesn´t change it to the new url. Same for a whole new scenarios. Seems like the lock and save button doesn´t work here.

return added scenario on api call

return added scenario on api call: /api/scenario/add/:issueID.
Related to the frontend bug in not showing the added scenario.

Run test functionality

As a user,
In want a button to run my scenarios
so I can see if my test passes

Delete scenarios

As a user,
I want to be able to delete scenarios
So I can get rid of them if they aren’t necessary anymore

Check stories and stepDefinitions (language)

Some stepDefinitions seems to be written in German.

Functionality and Code Review

(1) Checking the functionality of the application
(2) Simple Code Review in order to mark upcoming todos in the source code.

Gratis Versand

Als Premium Kunde erhalte ich freien Versand, wenn ich 5 B`cher bestelle

Reporting tool

As a user,
I want a visual reporting tool
So I am able to quickly see passed/ failed test cases

Deploy frontend application (Prototype 1)

Deploy frontend application on Heroku.

Templates

As a user,
I want a collection of templates
So I can easily select basic scenarios for testing my project

Presentation of the repo

First presentation of the repository and transfer to the organisation

Change POST on "/api/scenario/add/:scenarioID" to GET

In the current implementation adding a scenario via the API doesn´t take a new scenario from the body of the request. The new scenario is generated in backend. Therefore, we can change the call to GET.

Fix Bug: Input is copied in same step-templates.

adding more than 1 of the dame step tempaltes and editing the input changes all inputs.
Issue is only present while not posting the data to backend (saving) --> Frontend Bug.

Fix Delete Scenario

Deleting a scenario in the frontend does not delete the scenario in the database.