| Name | seano-formatter-qa-notes JSON |
| Version |
2.0.2
JSON |
| download |
| home_page | None |
| Summary | A Seano plugin that generates the QA Notes view |
| upload_time | 2025-01-20 23:36:59 |
| maintainer | None |
| docs_url | None |
| author | Andrew Keller |
| requires_python | >=3.0 |
| license | BSD 3-clause |
| keywords |
|
| VCS |
|
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
QA Notes Formatter Plugin for Seano
===================================
This project provides a Seano formatter named "QA Notes" which, given a query of
a Seano database, will generate a self-contained single-file HTML file
presenting an overview of what changes need Quality Assurance (QA) attention.
Intended Use Cases
------------------
The intended use case of this Seano View is one where it is easy to forget to
tell QA of one or more changes in the build you just sent them. This can happen
because you spent a month working on a single feature and your memory is fuzzy
on the early parts, or because you have multiple coworkers and you aren't an
expert in what they did. Regardless of why you forgot to tell QA about some
details, the common risks include:
1. QA can miss bugs, leading to the bugs reaching production
1. Product Managers can forget to inform other departments of changes
1. UX and/or Marketing can forget to inform customers of changes
1. When customers notice changes before employees do, it can make the project
look disorganized or unreliable.
Typical Workflow
----------------
At time of development, a developer writes testing notes in Seano. The notes
should be as thorough as reasonable: assume you might be on vacation when QA is
reading it.
Later, when QA gets a build, the build includes a machine-written HTML file
containing all of the testing notes written in this release, colloquially called
_the QA Notes_. QA reads these notes to know what to test.
Schema
------
The QA Notes view uses this schema for notes:
```yaml
---
# (OPTIONAL) URLs to an external ticketing system
tickets:
- https://example.com/tickets/EXAMPLE-1234
# (OPTIONAL) Customer-facing short release notes
customer-short-loc-hlist-md: # (or `customer-short-loc-hlist-rst` for RST)
en-US:
- Short sentence explaining this change to customers
- "This is an hlist, which means:":
- you can express a hierarchy here
# (REQUIRED) Employee-facing short release notes
employee-short-loc-hlist-md: # (or `employee-short-loc-hlist-rst` for RST)
en-US:
- Short sentence explaining this change to employees
- "This is an hlist, which means:":
- you can express a hierarchy here
# (OPTIONAL) Employee-facing long technical discussion
employee-technical-loc-md: # (or `employee-technical-loc-rst` for RST)
en-US: |
What was the problem? What solutions did you reject? Why did you choose
this solution? What might go wrong? What can Ops do to resolve an outage
over the weekend?
This field is a single large Markdown blob. Explaining details is good.
# (OPTIONAL) Customer Service-facing long technical discussion
mc-technical-loc-md: # (or `mc-technical-loc-rst` for RST)
en-US: |
What was the problem? What is the solution? What might go wrong? How can
Customer Service fix a problem over the weekend?
This field is a single large Markdown blob. Remember that Customer Service
watches over many products; be specific, but also be terse.
# (REQUIRED) QA-facing long technical discussion
qa-technical-loc-md: # (or `qa-technical-loc-rst` for RST)
en-US: |
What new features need to be tested? What old features need to be
regression-tested?
QA uses this section to perform QA, and also as a "diff" to update their
own test plan archives.
This field is a single large Markdown blob. Explaining details is good.
Assume that QA has zero knowledge of *what* to test, but that given that
knowledge, they know *how* to test it. Be specific in descriptions;
avoid generalizations when practical. Be as technical as you want.
If QA has questions, they'll ask you.
```
Testing Locally
---------------
Starting from scratch, this is how to set up local unit testing:
```sh
# Create and enter a virtual environment:
virtualenv .venv
. .venv/bin/activate
# Install this Seano formatter plugin in the virtual environment in "editable mode"
pip install -e .
# Install extra dependencies needed by the unit tests:
pip install -r ci_utest_requirements.txt
```
Then, going forward, you can run unit tests like this:
```sh
pytest
```
Raw data
{
"_id": null,
"home_page": null,
"name": "seano-formatter-qa-notes",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.0",
"maintainer_email": null,
"keywords": null,
"author": "Andrew Keller",
"author_email": "andrew@kellerfarm.com",
"download_url": "https://files.pythonhosted.org/packages/41/f6/5479c61f1dd07b2b2bcd92186e5228924a2d993c3c8d6559902dbc9004a9/seano_formatter_qa_notes-2.0.2.tar.gz",
"platform": null,
"description": "QA Notes Formatter Plugin for Seano\n===================================\n\nThis project provides a Seano formatter named \"QA Notes\" which, given a query of\na Seano database, will generate a self-contained single-file HTML file\npresenting an overview of what changes need Quality Assurance (QA) attention.\n\nIntended Use Cases\n------------------\n\nThe intended use case of this Seano View is one where it is easy to forget to\ntell QA of one or more changes in the build you just sent them. This can happen\nbecause you spent a month working on a single feature and your memory is fuzzy\non the early parts, or because you have multiple coworkers and you aren't an\nexpert in what they did. Regardless of why you forgot to tell QA about some\ndetails, the common risks include:\n\n1. QA can miss bugs, leading to the bugs reaching production\n1. Product Managers can forget to inform other departments of changes\n1. UX and/or Marketing can forget to inform customers of changes\n1. When customers notice changes before employees do, it can make the project\n look disorganized or unreliable.\n\nTypical Workflow\n----------------\n\nAt time of development, a developer writes testing notes in Seano. The notes\nshould be as thorough as reasonable: assume you might be on vacation when QA is\nreading it.\n\nLater, when QA gets a build, the build includes a machine-written HTML file\ncontaining all of the testing notes written in this release, colloquially called\n_the QA Notes_. QA reads these notes to know what to test.\n\nSchema\n------\n\nThe QA Notes view uses this schema for notes:\n\n```yaml\n---\n# (OPTIONAL) URLs to an external ticketing system\ntickets:\n- https://example.com/tickets/EXAMPLE-1234\n\n# (OPTIONAL) Customer-facing short release notes\ncustomer-short-loc-hlist-md: # (or `customer-short-loc-hlist-rst` for RST)\n en-US:\n - Short sentence explaining this change to customers\n - \"This is an hlist, which means:\":\n - you can express a hierarchy here\n\n# (REQUIRED) Employee-facing short release notes\nemployee-short-loc-hlist-md: # (or `employee-short-loc-hlist-rst` for RST)\n en-US:\n - Short sentence explaining this change to employees\n - \"This is an hlist, which means:\":\n - you can express a hierarchy here\n\n# (OPTIONAL) Employee-facing long technical discussion\nemployee-technical-loc-md: # (or `employee-technical-loc-rst` for RST)\n en-US: |\n What was the problem? What solutions did you reject? Why did you choose\n this solution? What might go wrong? What can Ops do to resolve an outage\n over the weekend?\n\n This field is a single large Markdown blob. Explaining details is good.\n\n# (OPTIONAL) Customer Service-facing long technical discussion\nmc-technical-loc-md: # (or `mc-technical-loc-rst` for RST)\n en-US: |\n What was the problem? What is the solution? What might go wrong? How can\n Customer Service fix a problem over the weekend?\n\n This field is a single large Markdown blob. Remember that Customer Service\n watches over many products; be specific, but also be terse.\n\n# (REQUIRED) QA-facing long technical discussion\nqa-technical-loc-md: # (or `qa-technical-loc-rst` for RST)\n en-US: |\n What new features need to be tested? What old features need to be\n regression-tested?\n\n QA uses this section to perform QA, and also as a \"diff\" to update their\n own test plan archives.\n\n This field is a single large Markdown blob. Explaining details is good.\n Assume that QA has zero knowledge of *what* to test, but that given that\n knowledge, they know *how* to test it. Be specific in descriptions;\n avoid generalizations when practical. Be as technical as you want.\n If QA has questions, they'll ask you.\n```\n\nTesting Locally\n---------------\n\nStarting from scratch, this is how to set up local unit testing:\n\n```sh\n# Create and enter a virtual environment:\nvirtualenv .venv\n. .venv/bin/activate\n\n# Install this Seano formatter plugin in the virtual environment in \"editable mode\"\npip install -e .\n\n# Install extra dependencies needed by the unit tests:\npip install -r ci_utest_requirements.txt\n```\n\nThen, going forward, you can run unit tests like this:\n\n```sh\npytest\n```\n",
"bugtrack_url": null,
"license": "BSD 3-clause",
"summary": "A Seano plugin that generates the QA Notes view",
"version": "2.0.2",
"project_urls": null,
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "a5bb4f2c3196db8dd37cb628c3f1131f4aed8eb6aae64f3023119d73bb5e08ab",
"md5": "4d83816d826b62e8da8707583665117c",
"sha256": "83cdaa9d89e641cab417e0f8782585c91ee7af8b3fc30256ebbcb255e60c9226"
},
"downloads": -1,
"filename": "seano_formatter_qa_notes-2.0.2-py3-none-any.whl",
"has_sig": false,
"md5_digest": "4d83816d826b62e8da8707583665117c",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.0",
"size": 31026,
"upload_time": "2025-01-20T23:36:57",
"upload_time_iso_8601": "2025-01-20T23:36:57.900004Z",
"url": "https://files.pythonhosted.org/packages/a5/bb/4f2c3196db8dd37cb628c3f1131f4aed8eb6aae64f3023119d73bb5e08ab/seano_formatter_qa_notes-2.0.2-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "41f65479c61f1dd07b2b2bcd92186e5228924a2d993c3c8d6559902dbc9004a9",
"md5": "ad06ae49b176d7b101924c9257f3e115",
"sha256": "ffa61a544dcc65506bc33bb0170a5b5c2f82bbd8048699315a3459bad1f2b428"
},
"downloads": -1,
"filename": "seano_formatter_qa_notes-2.0.2.tar.gz",
"has_sig": false,
"md5_digest": "ad06ae49b176d7b101924c9257f3e115",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.0",
"size": 26130,
"upload_time": "2025-01-20T23:36:59",
"upload_time_iso_8601": "2025-01-20T23:36:59.549398Z",
"url": "https://files.pythonhosted.org/packages/41/f6/5479c61f1dd07b2b2bcd92186e5228924a2d993c3c8d6559902dbc9004a9/seano_formatter_qa_notes-2.0.2.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-01-20 23:36:59",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "seano-formatter-qa-notes"
}
