Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC: Ideas to improve engineering productivity & participation #703

Open
atodorov opened this issue Jan 9, 2019 · 1 comment
Open

RFC: Ideas to improve engineering productivity & participation #703

atodorov opened this issue Jan 9, 2019 · 1 comment

Comments

@atodorov
Copy link
Member

@atodorov atodorov commented Jan 9, 2019

What makes a test engineer productive when they need to assess product risk and new features, when mapping product requirements documents (PRD) to test plans and test cases, when collaborating on user stories and behavior specification ? What makes developers, product owners, designers and other professionals productive when it comes to dealing with testing ?

For example consider the following workflow:

  • Company has idea for a new product
  • In case this is a big product it may have its own mission, i.e. what kind of problem is it trying to solve and for which group of customers
  • Product backlog is then created which outlines features that map to the product mission
  • Then the team, together with test engineers perform example mapping and discuss and refine the initial feature requirements. User stories are created
  • Behavior secification may also be created
  • Test plans and test cases are the immediate product of BDD specs and desired user stories

Later we iterate through the sprints and for each sprint something like this happens:

  • Desired product features are planned for development. They must be complete at least in terms of requirements, specs and tests
  • Devel writes code, maybe some unit tests, testers can also write automated tests and/or manually verify the current state of the feature being developed
  • Testing, including exploratory is performed before feature is merged
  • Rinse and repeat

Devel is also part of testing, right? Product owners, UX and interaction designers as well. Producing quality software product is a team effort!

This issue is for crazy ideas which will make testing (any part of the process) easier, more productive, less cumbersome. Also make it easier (or force you) to think differently when dealing with product activities so that this will benefit the final quality of the product.

Share, comment and 👍 below!

@atodorov
Copy link
Member Author

@atodorov atodorov commented Dec 27, 2020

@jeanpaul1304, @bgerrice you have upvoted this issue but the original description is too broad, not quite something actionable. Please share in more details how you imagine the proposed feature will work, e.g. what kind of workflow you would like to see. Without such information we're left to guess what people want and I'd rather close this issue instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant