Combine Manual and Automated Testing in Jira
You combine manual and automated testing in Jira by linking test apps to your project issues. Teams write manual steps in Jira and send automated build results through the API. Most teams set up a test plugin and share broad database credentials across test runners. When test roles have too much power, one bad script can alter live data. How to combine manual and automated testing in jira Jira tracks work through issues, stories, and bugs on a central project board. It does not store test cas
Automated Penetration Testing + Just-in-Time Access: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
You combine manual and automated testing in Jira by linking test apps to your project issues. Teams write manual steps in Jira and send automated build results through the API. Most teams set up a test plugin and share broad database credentials across test runners. When test roles have too much power, one bad script can alter live data.
How to combine manual and automated testing in jira
Jira tracks work through issues, stories, and bugs on a central project board. It does not store test cases or run test scripts out of the box. Teams add a test management app from the marketplace to fill this gap. This app creates a new issue type for test cases inside the project.
Testers write manual steps and expected outcomes right inside these test issues. They link each test issue to a user story or a bug ticket. For automated checks, developers keep test code in their version control system. The CI/CD pipeline runs these automated scripts whenever a developer pushes new code.
After the run finishes, the pipeline formats the test output as a report file. The pipeline then sends this report back to the Jira test app via REST API. The app reads the report and updates the status of each linked test issue. Managers see both manual pass rates and automated build results on one dashboard.
Why shared test environments create data risk
This workflow keeps project tracking clean and puts all test statuses in one place. Product owners can check release readiness by looking at a single Jira epic. Still, linking test results in Jira does not secure the test runners or testers. Both manual testers and CI/CD pipelines need to read and write staging data.
Teams often copy production data into staging databases so tests reflect real life. To move fast, teams give testers and CI/CD workers one shared database user. This shared user often holds wide read and write rights across all tables. Jira permissions only control who can edit test tickets on the web board.
Automated Penetration Testing + Just-in-Time Access: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Native Jira roles do not check what SQL queries a tester runs during a check. They also do not check what commands a CI/CD script runs against staging servers. If a staging database holds real emails, phone numbers, or card numbers, anyone can read them. A broken automated script can also drop tables and halt manual testing for everyone.
Securing database and server access during test runs
To fix this, teams must separate Jira ticket access from backend system access. Every tester and automated runner should use a unique identity for database sessions. Teams should check every query and command at the moment it runs. Data masking can rewrite emails, phone numbers, and card numbers in query results.
This stops test logs and Jira bug attachments from leaking private customer info. Teams can also block drop commands while allowing standard read and update statements. Tying each database action to a person or pipeline job makes audits simple. When a test fails or breaks data, you know which run caused the problem.
Check database and API queries on the wire
Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev runs beside those services as an open-source proxy, a sidecar for your Postgres or API. It inspects requests coming in and results going back on the wire.
Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run. On responses, hoop.dev data masking rewrites matched sensitive values in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.
Frequently asked questions
Can Jira run automated tests on its own?
No, Jira tracks issues and stories rather than running code. Your CI/CD tool runs the test scripts and sends the results to Jira via API.
How do manual testers link bugs to automated test failures?
When an automated test fails, the test app marks the Jira test issue as failed. A tester can then create a bug ticket and link it to that test issue.
How do we protect customer data during manual testing for Jira tickets?
Use dynamic data masking on the databases that your testers query during checks. Masking rewrites matched fields like emails and card numbers in query results.