Improvising developer’s effort
Dated: 10/02/2019
Overview
When comes to SDLC, time is very efficient. This “Dev-work-tracker” is the efficient way to reduce time specially on testing phase.
In many scenarios, same bug caught at different releases by the tester. Which means developers can make same mistakes gain and gain. The frequency of the developer tent to concentrate lesser on not interesting stuff.Example many developers excited about writing codes, but same excitement will be lacking when comes to writing unit test code. This leads to cause more bugs in the testing cycle.
In this case, “Dev-work-tracker” will help to track assignee’s bug history and compare them (using natural language processing - NLP) with his current task, then it will create a sub-task in this current task stating - “You have more than one bug history related to the current task, please make sure this won’t render in current task”.
Example:
Current Task - UI Development - positioning img.
If Assignee’s Bug History - 10
Out of 10, 4 is related to UI Development
Out of 4, 2 is related to positioning.
So this 2 positioning bugs will send it to Assignee’s eye, so that he can avoid this mistake again in his current work.
Dependencies
Install the package by running:
pip install dev-work-tracker
OR
shell sudo python3 setup.py install
Install the dependencies:
pip install jira pip install spacy python -m spacy download en_core_web_sm
Python standard dependencies:
devtracker
This package is to track developers work rate
Free software: MIT license
Documentation: (COMING SOON!) https://dev-work-tracker.readthedocs.org.
Maintainers
Jagadeesh Lakshminarasimhan - jagadeeshlaks@gmail.com
USAGE
from devtracker.devtracker import Trigger
jira_server = “https://example.atlassian.net/”
jira_user = “example@gm.com”
jira_password = “examplePassW@rd”
Issue_ID = “EXAM-1234” #Jira Issue ID
description = ‘This is sample description about the issue’
session = Trigger().jira_login(jira_server, jira_user, jira_password)
out = Trigger().windfall(Issue_ID, session, description)
print(out)
Metadata
Release files for dev-work-tracker 2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dev-work-tracker-2.0.tar.gz | 7.0 kB | Without provenance | Details for dev-work-tracker-2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dev_work_tracker-2.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for dev_work_tracker-2.0-py2.py3-none-any.whl |
Total release size: 14.0 kB
Release files / dev-work-tracker-2.0.tar.gz
| Download URL | dev-work-tracker-2.0.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a2d2482807063d1c91bc8ab6c83901d5ed6b60da2b4348368f25ad59301afe13
|
|
BLAKE2b-256 checksum How to use checksums |
1526664616b46ae0a8da1e568eb48b9926da0cd38250ccec6bd251800ccdd4d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.20.1 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.7.3
|
Release files / dev_work_tracker-2.0-py2.py3-none-any.whl
| Download URL | dev_work_tracker-2.0-py2.py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
12e4780c9c1372c3c722e8329a9b5c4893ce705ea809700bd1eb653d98028f8f
|
|
BLAKE2b-256 checksum How to use checksums |
90cf5ffaa49a348ece9f19a8aad012a27ee47ea7ae1f795d413631e8c2d5610d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.20.1 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.7.3
|
Security for dev-work-tracker 2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.