Manage your testing process easier.
Hi, Habrazhiteli!
Last month we did a huge amount of work to make testing sites and software on the Fixber site more convenient and much more efficient.
In this article we want to talk about what's new with us.
')
Welcome under cat.
1. black and white customer list
The customer got the opportunity to add the tester to the white or black list .
Adding a tester to the list takes place on the user details page.
If the tester is on the white list of the customer, then he is automatically connected to the closed projects of the customer without waiting for the application.
Defects from testers from the white list for the customer will be marked in green.
If the tester is on the black list of the customer, he will not be able to connect to the customer’s projects, as well as add comments and bugs for previously connected projects.
2. list of known problems for the project
On the project creation page, the “Problem List” field has been added, which will remind the customer to indicate a list of known problems in the project, which will not be accepted by them.
The more detailed the information, the fewer questions will be in the testing process.
3. rejection of the duplicate bug
In case of refusal from the customer of the bug due to a “duplicate”, the obligation to fill the field with the number of the original purchased bug was introduced.
Otherwise, to fail on such bugs will not work.
4. for projects added categories
The customer can group their projects at their discretion, specifying the "category" when adding / editing a project.
It is very convenient, for example, to give several projects for testing usability, combining them into one category of "usability".
The page of projects is altered and given completely to one customer, other customers of projects will not see.
5. project list improved
List of works that have become available to customers:
- “general testing” (functionality, security, workload, SEO),
- “security testing” (general security, penetration test),
- “documentation testing” (TZ, test cases),
- source code analysis,
- usability testing,
- localization testing.
The customer can split his project into several, adding to each of them the necessary list of works.
Example:
The customer is required to test the online store (functionality, penetration test and usability testing).
He adds 3 projects:
- the first with a list of works "general testing", choosing only "functionality",
- the second with the list of works “safety testing”, selecting only “penetration test”,
- the third with a list of works "usability testing."
After that, managing the list of bugs will be much easier, faster and more efficient.
6. restrictions on project approval and redemption of bugs
The customer can add a project to the site, but it can only be approved if there is a minimum amount on the customer’s account that will later be spent on buying bugs.
Before viewing and buying new bugs, customers will need to decide on previously added bugs or top up an account with the total amount of unavailable bugs.
7. facebook account
Entrance to the site was made possible without registering with a facebook account.
8. risk level for customer
If the customer has conducted on-site testing of several projects or one (several rounds) and is well versed in the process of working with testers, then the minimum risk level is set for him and the restrictions specified in clause 6 (restrictions on buying back bugs for customers) are removed.
9. selective access to projects
Some projects are not visible in the general list, access to them will be provided only to those testers who are suitable for the presence of certain knowledge and skills.
The more thoroughly and truthfully testers complete their profile, the more likely they are to take part in interesting projects.
Competition in such projects on the part of testers will be lower, which means that the quality of testing will be higher.
PS As always, we will be happy to hear all suggestions and comments on the site.
You can also see the previous list of improvements .
Thank you all and have a great Friday.
Last month we did a huge amount of work to make testing sites and software on the Fixber site more convenient and much more efficient.
In this article we want to talk about what's new with us.
')
Welcome under cat.
1. black and white customer list
The customer got the opportunity to add the tester to the white or black list .
Adding a tester to the list takes place on the user details page.
If the tester is on the white list of the customer, then he is automatically connected to the closed projects of the customer without waiting for the application.
Defects from testers from the white list for the customer will be marked in green.
If the tester is on the black list of the customer, he will not be able to connect to the customer’s projects, as well as add comments and bugs for previously connected projects.
2. list of known problems for the project
On the project creation page, the “Problem List” field has been added, which will remind the customer to indicate a list of known problems in the project, which will not be accepted by them.
The more detailed the information, the fewer questions will be in the testing process.
3. rejection of the duplicate bug
In case of refusal from the customer of the bug due to a “duplicate”, the obligation to fill the field with the number of the original purchased bug was introduced.
Otherwise, to fail on such bugs will not work.
4. for projects added categories
The customer can group their projects at their discretion, specifying the "category" when adding / editing a project.
It is very convenient, for example, to give several projects for testing usability, combining them into one category of "usability".
The page of projects is altered and given completely to one customer, other customers of projects will not see.
5. project list improved
List of works that have become available to customers:
- “general testing” (functionality, security, workload, SEO),
- “security testing” (general security, penetration test),
- “documentation testing” (TZ, test cases),
- source code analysis,
- usability testing,
- localization testing.
The customer can split his project into several, adding to each of them the necessary list of works.
Example:
The customer is required to test the online store (functionality, penetration test and usability testing).
He adds 3 projects:
- the first with a list of works "general testing", choosing only "functionality",
- the second with the list of works “safety testing”, selecting only “penetration test”,
- the third with a list of works "usability testing."
After that, managing the list of bugs will be much easier, faster and more efficient.
6. restrictions on project approval and redemption of bugs
The customer can add a project to the site, but it can only be approved if there is a minimum amount on the customer’s account that will later be spent on buying bugs.
Before viewing and buying new bugs, customers will need to decide on previously added bugs or top up an account with the total amount of unavailable bugs.
7. facebook account
Entrance to the site was made possible without registering with a facebook account.
8. risk level for customer
If the customer has conducted on-site testing of several projects or one (several rounds) and is well versed in the process of working with testers, then the minimum risk level is set for him and the restrictions specified in clause 6 (restrictions on buying back bugs for customers) are removed.
9. selective access to projects
Some projects are not visible in the general list, access to them will be provided only to those testers who are suitable for the presence of certain knowledge and skills.
The more thoroughly and truthfully testers complete their profile, the more likely they are to take part in interesting projects.
Competition in such projects on the part of testers will be lower, which means that the quality of testing will be higher.
PS As always, we will be happy to hear all suggestions and comments on the site.
Write to us , read us .
You can also see the previous list of improvements .
Thank you all and have a great Friday.
Source: https://habr.com/ru/post/122577/
All Articles