Post by account_disabled on Mar 14, 2024 8:33:00 GMT
Tests and preparation for launch All this had to be done very quickly. Although the client portal update was long overdue we had a rather limited time to launch and implement it. We prepared clickable layouts tested them choosing options for lists and request forms the UI was treated responsibly from the point of view of developing a new system. Autotests are written in Java the Maven collector is used. The test writing framework is TestNG and Selenium WebDriver is also used. Autotests are carried out on the functionality of the client portal in the UI. Currently approximately of all regression tests.
On the client portal are covered. UX testing was carried out on CROC employees not belonging to service Buy Email List departments. The company is large and you can go to conventional accountants and collect an unbiased opinion from them. About the features of the move At first not everyone was told about the move a couple of months before the launch active authors of applications were selected and letters were written to them with an offer to test the new client portal. At the same time they stipulated that the old service also works and all links still point to it. Feedback was collected through a simple form with the ability to rate and write a review.
Thanks to this form we also prioritized bug fixes. to report a problem it means that this bug really hurts and needs to be dealt with as soon as possible. Thanks to this form we have also prioritized bug fixes. If users reached it to report a problem it means that this bug really hurts and it needs to be dealt with as soon as possible. So users highlighted a lot of problem areas Old cases are not saved. I want to see what they did and how screenshots logs recommendations. Situations sometimes repeat themselves but the case is no longer on the portal. When Jira responds to a case by mail the status does not change it hangs in the status of waiting for the client.
On the client portal are covered. UX testing was carried out on CROC employees not belonging to service Buy Email List departments. The company is large and you can go to conventional accountants and collect an unbiased opinion from them. About the features of the move At first not everyone was told about the move a couple of months before the launch active authors of applications were selected and letters were written to them with an offer to test the new client portal. At the same time they stipulated that the old service also works and all links still point to it. Feedback was collected through a simple form with the ability to rate and write a review.
Thanks to this form we also prioritized bug fixes. to report a problem it means that this bug really hurts and needs to be dealt with as soon as possible. Thanks to this form we have also prioritized bug fixes. If users reached it to report a problem it means that this bug really hurts and it needs to be dealt with as soon as possible. So users highlighted a lot of problem areas Old cases are not saved. I want to see what they did and how screenshots logs recommendations. Situations sometimes repeat themselves but the case is no longer on the portal. When Jira responds to a case by mail the status does not change it hangs in the status of waiting for the client.
