From the course: Ebook Quality Assurance
Unlock the full course today
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
How to report issues you find
- [Instructor] When you find issues in your testing it is important that you give accurate and usable change details to the development team so they can easily find the issues and fix them. I always recommend including the following in your change reports. The page number in the source book. This helps the developer know where to go in the source book to see what the problem is supposed to look like there. If your eBook's include a page list as I recommend, then the page number can also help the developer more easily locate the same location in the eBook code. A description of the issue or error, including some unique searchable text. The description should be as detailed as necessary and include screenshots as needed. The searchable text here is important, as searching is the easiest way for the developer to find a specific location in the code. A description of the change being requested. If there's a spelling error, spell the word correctly. If something needs to be moved, describe…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
-
-
-
-
-
-
(Locked)
Recommended QA workflow2m 9s
-
(Locked)
QA step 1: The big picture2m 16s
-
(Locked)
QA step 2: Fonts and special characters5m 25s
-
(Locked)
QA step 3: Structure3m 30s
-
(Locked)
QA step 4: Images2m 31s
-
(Locked)
QA step 5: Tables and charts1m 56s
-
(Locked)
QA step 6: Front matter and back matter3m 51s
-
(Locked)
QA step 7: Media and interactivity3m 43s
-
(Locked)
QA step 8: Fixed layout1m 52s
-
(Locked)
QA step 9: Accessibility2m 25s
-
(Locked)
Creating your own QA checklists2m 43s
-
(Locked)
How to report issues you find1m 59s
-
(Locked)
-