Tuskr Roadmap

Add the ability set a test case type as default.

Display account deletion warning in the UI for users on the free plan.

Support “need-to-know” testing

Due to the sensitivity of certain test cases, the confidentiality of upcoming functionalities, or for other reasons, it is crucial testers see only those test cases assigned to them. This functionality is designed to provide granular control over access, such that testers will only be able to see the test cases in test runs that they are assigned to.

Improve Test Run Reporting

End users will be able to include fields of their choice for test cases in the test run report. This is especially useful for industries that demand evidence of testing being actually done in a test run. For example – medical device testing.

Automatically add new users to project

New users need to be explicitly added to projects. For small teams or for certain projects, this becomes tedious. This functionality allows project managers to mark projects to which newly created users should automatically be added. When they are added to these projects, they will be assigned their default role in those projects.

Make it convenient to add all users to the project team

Added the “– All Users –” option in the “Add User” dropdown in the project’s “Access” area so that you can add all users in one shot.

Add search capability in the toolbar.

Provide a way for users to search and quickly jump to a project, test run, suite or test case.

Integrations

Import J-Unit XML.

Allow import of J-Unit XML reports. This will include automatic provisioning of test cases, suites and sections as well as test run reporting. With this functionality, it will be easy to integrate with populate automation frameworks like Pytest, Jenkins, etc.

Show more test run information on the test run page.

Show description, deadline and other test run attributes on the test run page.

Add and show descriptions for suites and sections.

Display run history information for test cases.

Provide a way to see when the test cases have failed or succeeded. This will help identify problem points.

Add search capability in the toolbar.

Provide a way for users to quickly jump to a project, test run, suite, section or a test case.

Two-factor authentication (2FA)

To enhance security, an email-based two-factor authentication (2FA) mechanism should be implemented. This feature will require users to enter a unique code, sent to their registered email address, in addition to their password, to successfully authenticate themselves. By implementing this form of 2FA, the risk of unauthorized access and potential data breaches can be significantly reduced.

Customisable session timeouts

Administrators of an organization should have the ability to configure the inactivity timeout, which determines the period of time of inactivity after which user sessions will be automatically terminated.

Single sign-on (SSO) based authentication

Allow setting up of Single Sign-On supporting the SAML 2.0 standard.

Allow access only from restricted IPs

Only allow access from user-entered IPs or network addresses.

Password Rules

Allow users to customise password policies like min length, etc.

Import “.feature” files

Allow importing of cucumber feature files.