Top-notch Test Case
Management System

Hi!

As we are constantly developing our service, soon our integration will get some changes.

The only thing you would need to do – just get Access Token and connect your integration again.

Here how you can get your Access Token in relevant integrations:

Redmine Access Token

1) Click the Administration link in the header

2) Click the ‘Settings’ link in the menu

3) Click the ‘Authentication’ tab

4) Check the ‘Enable REST web service’ checkbox and save changes

5) Go to your account page and generate an API access key

Jira Cloud Token

1) Go to ‘Account Settings’ page

2) Select the ‘Security’ tab and click the ‘Create and manage API tokens’ link

3) Click ‘Create API Token’ button and create a token

YouTrack Access Token

1) Go to the Profile page

2) Click the ‘Update personal information and manage logins’ link on the ‘General’ tab

3) Select the ‘Authentication’ tab and click the ‘New token’ button

If you’ll need assistance on this topic – say us “hello” support@testcaselab.com

Select features you would like to have in TestCaseLab here: Link

Tell us what you think here: Link

Leave feedback on Capterra

‍

Welcome to the TestCaseLab team!

Today in a short test case tutorial we are going to discuss how to write effective test cases. It would be useful for everyone who ever wondered how to write test cases in test case writing tools. Writing effective test cases will help whoever is executing the test case.

These are tips which may help you write better and more effective test cases:

1) To start off you should have 3-8 steps in a test case. If you have less than 3 test steps, use a checklist instead.  

2) When you write a test case, pay attention if the test result is obvious, then you don’t need to specify an expected result of each step. However, when testers report defects based on a test case, they should indicate which test step failed. This will make troubleshooting easier.

3) Your test case may have too many steps. Then you should divide it. You can use smaller sets or groups. It is important because if an error occurs somewhere, it gets confusing for the developer who has to fix the bug as well as future testers who have to repeat all the steps to test it.

4) Only use preconditions if you need them. For example, if you have to load a set of customers into the system before testing begins, then you need pre-conditions. If not – leave the field blank.

That’s it.

Follow these tips and we are sure you’ll be writing effective test cases in online test case writing tools in no time.

Looking for a test case tool?

Our testcase tool can assist you with testing:

TestCaseLab is a test case management tool that allows you to manage your test cases, test plans, as well as test runs in the web application and reports cases to a bug-tracking tool if needed. It also makes testing more organized so you could keep a high-quality product.

Tclab pricing starts from $48 with unlimited users, you can invite as many colleagues as you need in tc-lab.

Get your 30 days free trial just here – case lab

Watch quick overview here – https://www.youtube.com/watch?v=ZF4hDsY3mqc

Hope this helps 👍

Hey! How about visiting a great QA conference with a free track and TCLab’s discount?
🎁  For our lovely users, we offer the Promo Code – TCL15 to get a 15% discount!

QA Global Summit

QA Global Summit 2021 by Geekle is a 2 days dive into the latest QA insights: building QA from scratch; Testing Data with AI; QA career – path turns to take; Testing through the lens of business…

What’s waiting for you:

2 tracks: FREE Entry Level OR Full Access Pass starting from just $49

14 hours of NON-STOP tech talks from world-class speakers

40+ speakers from Top Companies from all over the world

All this and much more here https://qa.geekle.us/

‍

5 Reasons To Use A Test Case Management System Instead Of A Spreadsheet

It’s never too late to make a switch from your traditional spreadsheet to a reliable test case management software. By doing so, developers can properly oversee, control, track and grasp the entire platform testing process.

The best test management tool allows engineers to easily create and operate test cases, organize tests and requirements, curate their own dashboard and produce bugs directly from test runs to significantly decrease QA time and enhance product quality.

With all these advantages and more, there’s no excuse for your company to fall behind product development. Let’s learn how test case management tools play a crucial role in building a defect-free and usable software product and how they can be a major upgrade to your regular spreadsheet.

Reason 1 – Spreadsheets are not designed for test case

Traditionally, established organizations depended on spreadsheets and collaborative tools for test case management; however, matters quickly fell apart and software QA engineers realized they were devoting huge chunks of time trying to make the method work that they couldn’t concentrate on testing itself.

To use spreadsheets for test cases, you need a huge amount of sheets to manage. Inconsistent data is also a big problem for your organization since a systematic approach is missing when it comes to modifying documents. This will negatively influence your test results. These are just some of the downsides of using a spreadsheet for developing your software.

Test case management software offers an array of functional features, integrations and riveting capabilities, but most importantly, it is equipped with the most critical feature that instantly supplies you with data fields and informs you regarding which data you should retrieve and monitor. The moment you acquire and launch your system, you’ll have an entire roster of necessary information in your hands.

Additionally, you’ll also have functions that allow you to easily capture, keep, track and look up this necessary information. You can also use your test case management tools as a bug tracking system or as a means for source control. You’ll also get to resolve the issues that come with settling for mere spreadsheets.

Reason 2 – Bulk action

Test case management tools provide complete control over every element of your testing process from test generation, scheming and execution via defect submission and conclusion. Managing the entire quality lifecycle, an adequate test case management platform allows engineers to successfully meet shorter deadlines, tackle complicated present-day testing challenges and enhance your software product.

Features that contribute to this include bulk actions. Bulk actions allow engineers to efficiently accomplish multiple actions simultaneously compared to executing and completing the same action multiple times.

Goodfirms revealed that on average, engineers develop software for 4.5 months. Keep up with that figure or make it faster with bulk actions and automated processes that can be provided by test case management systems.

As opposed to spreadsheets, test case management systems allow developers to edit, exclude and delete cases in groups. They also offer functions that provide bulk or inline editing, which also adds to increased productivity, enabling teams to crunch numbers and release software with enhanced quality in the most timely fashion.

Reason 3 – Effective collaboration

Successful test case management also spans fruitful test team management. Spreadsheets don’t have collaborative capabilities that enable this. For instance, if you want to share your sheets with fellow programmers, you need to do it via emails, which can be cumbersome. Your team might also end up working with different versions of spreadsheets with inconsistent untimely data.

Test case management tools streamline this by providing a systematized approach to test efforts, thanks to collaborative work functions such as real-time synchronization and the ability to lock elements that are being modified by another user. They also offer reporting tools that help you track your test cases as a unit. You can even set up an integration with collaborative tools such as Trello.

A survey from Codingsans reveals that 66.67% of startups use email as a means of communication for their teams. You can get out of that and upgrade to the best test management tool instead.

Apart from this, users can also issue tests, monitor test execution and manage delegated teams, which is critical nowadays since software development initiatives now commonly cover more than one team or one project site. Having a highly organized test management drives team productivity throughout the testing process.

Reason 4 – Get an outlook on progress

A solid perspective on progress is vital for test case management. With a test case management software, you can easily view progress through various tools such as a configurable dashboard that displays test run results or an easy-to-use test case searching solution that flashes cases and their status by name, description or tags.

At the push of a button, test case management tools can supply engineers with a robust overview of the status of their test efforts as well as additional information on test construction, execution, progress, scope and quality of requirements. With a reliable platform, you can say goodbye to inconsistent data that stems from managing a large volume of spreadsheets that contain inaccurate data.

Additionally, some test case management systems supply professional progress charts in their reporting capabilities. You can take your operations even further by looking through this list of top 10 business management solutions for 2020.

Reason 5 – Solid functions for monitoring

A core advantage of test case management software is the ability to delegate tasks and monitor tasks across your software development team. While you might be using spreadsheets to do this, the entire process of emailing one colleague for updates can be time-consuming and tiresome, so it pays to have a platform where you can do this too.

Following this, it’s also important for your organization to be able to monitor test executions and outcomes. This translates to monitoring test runs, issues, running over bugfixes for validation, as well as documenting successful tests.

Worth the investment

Although we can’t deny that spreadsheets are useful, it’s just not the tool for managing test cases. Test case management tools will significantly streamline testing complex software because they are designed to do so by smoothly fusing with your current tool stack and propelling your company to increase productivity and efficiency.

Some test case management software companies will try to get you to use their own platforms, but here at TestCaseLab, the choice is in your hands. You know your organization better than we do, but we strongly recommend ditching the spreadsheet and investing in a good test case management software.

If you want to know more about us, check out what TestCaseLab is and find out why you need it.

👋  Hi!
I hope you’re having a great week.
This month we’ve made an effort to improve our API and Test Case Lab in general.

Here are some of the TCL API improvements:

➕   Now you can make single and bulk assignments of the Test Cases to the Test Run using API.
➕   New endpoint for adding Test Plan(s) to the Test Run was released.
➕   Now you can find the user ‘id’ in the response of GET /users request.

📍 For more details on API updates please visit our API Documentation

API reference

Other good news on TCLab:

➕  Now you can copy Test Suite with all the test cases and nesting Suites. This feature will make test case management easier.
➕  Your company Admin and Owner would have an ability to filter Activity Stream of the users and see all their activity for the project(s). In order to see the stream click the ‘Gear’ icon in the top right corner and go to the ‘Users’ page. Select any user and open ‘Activity Stream’ tab.
➕  API token generation flow was changed. Only the Company Owner or Admin can generate it.
In order to do it click the ‘Gear’ icon in the top right corner and go to the ‘Company Profile’ page. Click the ‘Show API Tokens’ button and you’ll see the list of your tokens and ability to generate a new one.

API Generation

⁉️  What will happen next?

It depends on you!
➕  Select features you would like to have in test case tool here: Link

🎤  Tell us what you think Here

🙋‍♀  Leave feedback about TCL on Capterra
📩  Say us “hello” support@testcaselab.com

Hey! How about visiting a great QA conference with a free track and TCLab’s discount?
🎁  For our lovely users, we offer the Promo Code – TCL15 to get a 15% discount!

QA Global Summit

QA Global Summit 2021 by Geekle is a 2 days dive into the latest QA insights: building QA from scratch; Testing Data with AI; QA career – path turns to take; Testing through the lens of business…

What’s waiting for you:

2 tracks: FREE Entry Level OR Full Access Pass starting from just $49

14 hours of NON-STOP tech talks from world-class speakers

40+ speakers from Top Companies from all over the world

All this and much more here https://qa.geekle.us/

‍

Welcome to the TestCaseLab team!

Today in a short test case tutorial we are going to discuss how to write effective test cases. It would be useful for everyone who ever wondered how to write test cases in test case writing tools. Writing effective test cases will help whoever is executing the test case.

These are tips which may help you write better and more effective test cases:

1) To start off you should have 3-8 steps in a test case. If you have less than 3 test steps, use a checklist instead.  

2) When you write a test case, pay attention if the test result is obvious, then you don’t need to specify an expected result of each step. However, when testers report defects based on a test case, they should indicate which test step failed. This will make troubleshooting easier.

3) Your test case may have too many steps. Then you should divide it. You can use smaller sets or groups. It is important because if an error occurs somewhere, it gets confusing for the developer who has to fix the bug as well as future testers who have to repeat all the steps to test it.

4) Only use preconditions if you need them. For example, if you have to load a set of customers into the system before testing begins, then you need pre-conditions. If not – leave the field blank.

That’s it.

Follow these tips and we are sure you’ll be writing effective test cases in online test case writing tools in no time.

Looking for a test case tool?

Our testcase tool can assist you with testing:

TestCaseLab is a test case management tool that allows you to manage your test cases, test plans, as well as test runs in the web application and reports cases to a bug-tracking tool if needed. It also makes testing more organized so you could keep a high-quality product.

Tclab pricing starts from $48 with unlimited users, you can invite as many colleagues as you need in tc-lab.

Get your 30 days free trial just here – case lab

Watch quick overview here – https://www.youtube.com/watch?v=ZF4hDsY3mqc

Hope this helps 👍

Hi!
I hope you’re having a great week.

We’ve released new features that you asked us about:

+ Assign users to ‘view only’ project role;
+ Add multiple test plans while creating the test run;
+ Use the full-screen mode for editing Test Cases;
+ Use filtering properties to URL to share the custom search result;
+ Archive test plans or test runs to keep your desk clean.

1) Sometimes you want users not to do any actions in the project except viewing the test cases, test plans or test runs.
So we’ve added a new project ‘Viewer’ role with only view permission.
We commend our lovely clients Anna, Nikita, Hiro and Rich for their ideas.

2) Now you have the ability to add multiple test plans while creating the test run. We think it will come in handy!

️️ 3) Have a big picture while working with details – now you can work with the test case in full-screen mode and focus only on the data related to it.

4) Copy the URL with all the filter properties applied and share it with your team members.
We commend our lovely client Chinna Raj for his idea.

️️5) Have multiple test plans or test runs that aren’t in use and you don’t want to delete them? Can’t find needed active test runs or plans between all of them?
This new feature of archiving test plans and runs exactly for you!
You can easily hide non-active test plans or test runs from the list by clicking the ‘Archive’ button.
⏰ They won’t be deleted and be displayed in the separate archived list where you can find them later.

⁉️ What will happen next?

It depends on you!

Select features you would like to have in TestCaseLab here: Link

Tell us what you think Here

Leave feedback on Capterra
Say us “hello” support@testcaselab.com

‍

Hi!
I hope you’re having a great week.

We’ve released new features that you asked us about:

+ Assign users to ‘view only’ project role;
+ Add multiple test plans while creating the test run;
+ Use the full-screen mode for editing Test Cases;
+ Use filtering properties to URL to share the custom search result;
+ Archive test plans or test runs to keep your desk clean.

1) Sometimes you want users not to do any actions in the project except viewing the test cases, test plans or test runs.
So we’ve added a new project ‘Viewer’ role with only view permission.
We commend our lovely clients Anna, Nikita, Hiro and Rich for their ideas.

2) Now you have the ability to add multiple test plans while creating the test run. We think it will come in handy!

️️ 3) Have a big picture while working with details – now you can work with the test case in full-screen mode and focus only on the data related to it.

4) Copy the URL with all the filter properties applied and share it with your team members.
We commend our lovely client Chinna Raj for his idea.

️️5) Have multiple test plans or test runs that aren’t in use and you don’t want to delete them? Can’t find needed active test runs or plans between all of them?
This new feature of archiving test plans and runs exactly for you!
You can easily hide non-active test plans or test runs from the list by clicking the ‘Archive’ button.
⏰ They won’t be deleted and be displayed in the separate archived list where you can find them later.

⁉️ What will happen next?

It depends on you!

Select features you would like to have in TestCaseLab here: Link

Tell us what you think Here

Leave feedback on Capterra
Say us “hello” support@testcaselab.com

‍

Welcome to the TestCaseLab team!

Today in a short test case tutorial we are going to discuss how to write effective test cases. It would be useful for everyone who ever wondered how to write test cases in test case writing tools. Writing effective test cases will help whoever is executing the test case.

These are tips which may help you write better and more effective test cases:

1) To start off you should have 3-8 steps in a test case. If you have less than 3 test steps, use a checklist instead.  

2) When you write a test case, pay attention if the test result is obvious, then you don’t need to specify an expected result of each step. However, when testers report defects based on a test case, they should indicate which test step failed. This will make troubleshooting easier.

3) Your test case may have too many steps. Then you should divide it. You can use smaller sets or groups. It is important because if an error occurs somewhere, it gets confusing for the developer who has to fix the bug as well as future testers who have to repeat all the steps to test it.

4) Only use preconditions if you need them. For example, if you have to load a set of customers into the system before testing begins, then you need pre-conditions. If not – leave the field blank.

That’s it.

Follow these tips and we are sure you’ll be writing effective test cases in online test case writing tools in no time.

Looking for a test case tool?

Our testcase tool can assist you with testing:

TestCaseLab is a test case management tool that allows you to manage your test cases, test plans, as well as test runs in the web application and reports cases to a bug-tracking tool if needed. It also makes testing more organized so you could keep a high-quality product.

Tclab pricing starts from $48 with unlimited users, you can invite as many colleagues as you need in tc-lab.

Get your 30 days free trial just here – case lab

Watch quick overview here – https://www.youtube.com/watch?v=ZF4hDsY3mqc

Hope this helps 👍

It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout. The point of using Lorem Ipsum is that it has a more-or-less normal distribution of letters, as opposed to using 'Content here, content here', making it look like readable English. Many desktop publishing packages and web page editors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in their infancy. Various versions have evolved over the years, sometimes by accident, sometimes on purpose (injected humour and the like).

Hey! How about visiting a great QA conference with a free track and TCLab’s discount?
🎁  For our lovely users, we offer the Promo Code – TCL15 to get a 15% discount!

QA Global Summit

QA Global Summit 2021 by Geekle is a 2 days dive into the latest QA insights: building QA from scratch; Testing Data with AI; QA career – path turns to take; Testing through the lens of business…

What’s waiting for you:

2 tracks: FREE Entry Level OR Full Access Pass starting from just $49

14 hours of NON-STOP tech talks from world-class speakers

40+ speakers from Top Companies from all over the world

All this and much more here https://qa.geekle.us/

‍

👋  Hi!
I hope you’re having a great week.
This month we’ve made an effort to improve our API and Test Case Lab in general.

Here are some of the TCL API improvements:

➕   Now you can make single and bulk assignments of the Test Cases to the Test Run using API.
➕   New endpoint for adding Test Plan(s) to the Test Run was released.
➕   Now you can find the user ‘id’ in the response of GET /users request.

📍 For more details on API updates please visit our API Documentation

API reference

Other good news on TCLab:

➕  Now you can copy Test Suite with all the test cases and nesting Suites. This feature will make test case management easier.
➕  Your company Admin and Owner would have an ability to filter Activity Stream of the users and see all their activity for the project(s). In order to see the stream click the ‘Gear’ icon in the top right corner and go to the ‘Users’ page. Select any user and open ‘Activity Stream’ tab.
➕  API token generation flow was changed. Only the Company Owner or Admin can generate it.
In order to do it click the ‘Gear’ icon in the top right corner and go to the ‘Company Profile’ page. Click the ‘Show API Tokens’ button and you’ll see the list of your tokens and ability to generate a new one.

API Generation

⁉️  What will happen next?

It depends on you!
➕  Select features you would like to have in test case tool here: Link

🎤  Tell us what you think Here

🙋‍♀  Leave feedback about TCL on Capterra
📩  Say us “hello” support@testcaselab.com

5 Reasons To Use A Test Case Management System Instead Of A Spreadsheet

It’s never too late to make a switch from your traditional spreadsheet to a reliable test case management software. By doing so, developers can properly oversee, control, track and grasp the entire platform testing process.

The best test management tool allows engineers to easily create and operate test cases, organize tests and requirements, curate their own dashboard and produce bugs directly from test runs to significantly decrease QA time and enhance product quality.

With all these advantages and more, there’s no excuse for your company to fall behind product development. Let’s learn how test case management tools play a crucial role in building a defect-free and usable software product and how they can be a major upgrade to your regular spreadsheet.

Reason 1 – Spreadsheets are not designed for test case

Traditionally, established organizations depended on spreadsheets and collaborative tools for test case management; however, matters quickly fell apart and software QA engineers realized they were devoting huge chunks of time trying to make the method work that they couldn’t concentrate on testing itself.

To use spreadsheets for test cases, you need a huge amount of sheets to manage. Inconsistent data is also a big problem for your organization since a systematic approach is missing when it comes to modifying documents. This will negatively influence your test results. These are just some of the downsides of using a spreadsheet for developing your software.

Test case management software offers an array of functional features, integrations and riveting capabilities, but most importantly, it is equipped with the most critical feature that instantly supplies you with data fields and informs you regarding which data you should retrieve and monitor. The moment you acquire and launch your system, you’ll have an entire roster of necessary information in your hands.

Additionally, you’ll also have functions that allow you to easily capture, keep, track and look up this necessary information. You can also use your test case management tools as a bug tracking system or as a means for source control. You’ll also get to resolve the issues that come with settling for mere spreadsheets.

Reason 2 – Bulk action

Test case management tools provide complete control over every element of your testing process from test generation, scheming and execution via defect submission and conclusion. Managing the entire quality lifecycle, an adequate test case management platform allows engineers to successfully meet shorter deadlines, tackle complicated present-day testing challenges and enhance your software product.

Features that contribute to this include bulk actions. Bulk actions allow engineers to efficiently accomplish multiple actions simultaneously compared to executing and completing the same action multiple times.

Goodfirms revealed that on average, engineers develop software for 4.5 months. Keep up with that figure or make it faster with bulk actions and automated processes that can be provided by test case management systems.

As opposed to spreadsheets, test case management systems allow developers to edit, exclude and delete cases in groups. They also offer functions that provide bulk or inline editing, which also adds to increased productivity, enabling teams to crunch numbers and release software with enhanced quality in the most timely fashion.

Reason 3 – Effective collaboration

Successful test case management also spans fruitful test team management. Spreadsheets don’t have collaborative capabilities that enable this. For instance, if you want to share your sheets with fellow programmers, you need to do it via emails, which can be cumbersome. Your team might also end up working with different versions of spreadsheets with inconsistent untimely data.

Test case management tools streamline this by providing a systematized approach to test efforts, thanks to collaborative work functions such as real-time synchronization and the ability to lock elements that are being modified by another user. They also offer reporting tools that help you track your test cases as a unit. You can even set up an integration with collaborative tools such as Trello.

A survey from Codingsans reveals that 66.67% of startups use email as a means of communication for their teams. You can get out of that and upgrade to the best test management tool instead.

Apart from this, users can also issue tests, monitor test execution and manage delegated teams, which is critical nowadays since software development initiatives now commonly cover more than one team or one project site. Having a highly organized test management drives team productivity throughout the testing process.

Reason 4 – Get an outlook on progress

A solid perspective on progress is vital for test case management. With a test case management software, you can easily view progress through various tools such as a configurable dashboard that displays test run results or an easy-to-use test case searching solution that flashes cases and their status by name, description or tags.

At the push of a button, test case management tools can supply engineers with a robust overview of the status of their test efforts as well as additional information on test construction, execution, progress, scope and quality of requirements. With a reliable platform, you can say goodbye to inconsistent data that stems from managing a large volume of spreadsheets that contain inaccurate data.

Additionally, some test case management systems supply professional progress charts in their reporting capabilities. You can take your operations even further by looking through this list of top 10 business management solutions for 2020.

Reason 5 – Solid functions for monitoring

A core advantage of test case management software is the ability to delegate tasks and monitor tasks across your software development team. While you might be using spreadsheets to do this, the entire process of emailing one colleague for updates can be time-consuming and tiresome, so it pays to have a platform where you can do this too.

Following this, it’s also important for your organization to be able to monitor test executions and outcomes. This translates to monitoring test runs, issues, running over bugfixes for validation, as well as documenting successful tests.

Worth the investment

Although we can’t deny that spreadsheets are useful, it’s just not the tool for managing test cases. Test case management tools will significantly streamline testing complex software because they are designed to do so by smoothly fusing with your current tool stack and propelling your company to increase productivity and efficiency.

Some test case management software companies will try to get you to use their own platforms, but here at TestCaseLab, the choice is in your hands. You know your organization better than we do, but we strongly recommend ditching the spreadsheet and investing in a good test case management software.

If you want to know more about us, check out what TestCaseLab is and find out why you need it.

Welcome to the TestCaseLab team!

Today in a short test case tutorial we are going to discuss how to write effective test cases. It would be useful for everyone who ever wondered how to write test cases in test case writing tools. Writing effective test cases will help whoever is executing the test case.

These are tips which may help you write better and more effective test cases:

1) To start off you should have 3-8 steps in a test case. If you have less than 3 test steps, use a checklist instead.  

2) When you write a test case, pay attention if the test result is obvious, then you don’t need to specify an expected result of each step. However, when testers report defects based on a test case, they should indicate which test step failed. This will make troubleshooting easier.

3) Your test case may have too many steps. Then you should divide it. You can use smaller sets or groups. It is important because if an error occurs somewhere, it gets confusing for the developer who has to fix the bug as well as future testers who have to repeat all the steps to test it.

4) Only use preconditions if you need them. For example, if you have to load a set of customers into the system before testing begins, then you need pre-conditions. If not – leave the field blank.

That’s it.

Follow these tips and we are sure you’ll be writing effective test cases in online test case writing tools in no time.

Looking for a test case tool?

Our testcase tool can assist you with testing:

TestCaseLab is a test case management tool that allows you to manage your test cases, test plans, as well as test runs in the web application and reports cases to a bug-tracking tool if needed. It also makes testing more organized so you could keep a high-quality product.

Tclab pricing starts from $48 with unlimited users, you can invite as many colleagues as you need in tc-lab.

Get your 30 days free trial just here – case lab

Watch quick overview here – https://www.youtube.com/watch?v=ZF4hDsY3mqc

Hope this helps 👍

Hi!

As we are constantly developing our service, soon our integration will get some changes.

The only thing you would need to do – just get Access Token and connect your integration again.

Here how you can get your Access Token in relevant integrations:

Redmine Access Token

1) Click the Administration link in the header

2) Click the ‘Settings’ link in the menu

3) Click the ‘Authentication’ tab

4) Check the ‘Enable REST web service’ checkbox and save changes

5) Go to your account page and generate an API access key

Jira Cloud Token

1) Go to ‘Account Settings’ page

2) Select the ‘Security’ tab and click the ‘Create and manage API tokens’ link

3) Click ‘Create API Token’ button and create a token

YouTrack Access Token

1) Go to the Profile page

2) Click the ‘Update personal information and manage logins’ link on the ‘General’ tab

3) Select the ‘Authentication’ tab and click the ‘New token’ button

If you’ll need assistance on this topic – say us “hello” support@testcaselab.com

Select features you would like to have in TestCaseLab here: Link

Tell us what you think here: Link

Leave feedback on Capterra

‍

Hi!
I hope you’re having a great week.

We’ve released new features that you asked us about:

+ Assign users to ‘view only’ project role;
+ Add multiple test plans while creating the test run;
+ Use the full-screen mode for editing Test Cases;
+ Use filtering properties to URL to share the custom search result;
+ Archive test plans or test runs to keep your desk clean.

1) Sometimes you want users not to do any actions in the project except viewing the test cases, test plans or test runs.
So we’ve added a new project ‘Viewer’ role with only view permission.
We commend our lovely clients Anna, Nikita, Hiro and Rich for their ideas.

2) Now you have the ability to add multiple test plans while creating the test run. We think it will come in handy!

️️ 3) Have a big picture while working with details – now you can work with the test case in full-screen mode and focus only on the data related to it.

4) Copy the URL with all the filter properties applied and share it with your team members.
We commend our lovely client Chinna Raj for his idea.

️️5) Have multiple test plans or test runs that aren’t in use and you don’t want to delete them? Can’t find needed active test runs or plans between all of them?
This new feature of archiving test plans and runs exactly for you!
You can easily hide non-active test plans or test runs from the list by clicking the ‘Archive’ button.
⏰ They won’t be deleted and be displayed in the separate archived list where you can find them later.

⁉️ What will happen next?

It depends on you!

Select features you would like to have in TestCaseLab here: Link

Tell us what you think Here

Leave feedback on Capterra
Say us “hello” support@testcaselab.com

‍