![]() ![]() As you know that the label was just created by your team and you also know that it has to be fixed anyway, report an issue straight away to make sure that the label will also be correct when deploying to acc and prod environments (and thus prevent further overhead). For end users this would cause a lot of confusion. While testing a new feature, you see that one of the text labels related to the new feature is incorrect. You are still working on the same eCommerce platform as in case 2. Your issue might not even be valid, as the content could be different on the production environment. Content like this is really the responsibility of the webmasters team and should not distract you from the work that you were really doing. The content is managed by a team of webmasters on the production environment and there is probably hundreds of pages with content like this. You observed this on the test environment. While testing, you see that one of the existing information pages of the website contains some spelling mistake. You are working on an eCommerce platform. Not correcting them will possibly give a bad customer experience to a lot of customers and it it will take a lot of time before all of the users have updated their device. In this context, it is highly important that the result of your testing (and rework) is that the software is as perfect as possible, including any typo's or spelling mistakes that you see. End users are only able to update the device by connecting it to a PC. ![]() ![]() After your approval, nobody else is going to test it. You are testing an electronic device that will be shipped with the software you are testing. It totally depends in what context you are at. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |