Write a detailed test plan for PDF text extractor application
Budget: $250 – $750 USD
Required skills
a) Experience writing test plans using a QA testers mindset - what could go wrong, how to break it, how to make it do something that the developer wasn't thinking of when they wrote the software.
b) Experience reading and interpreting detailed file specifications and interpreting beneath the covers how different aspects of the format work, and then conceiving test cases from that.
Job Overview
The purpose of the task is to prepare a detailed plan and test cases for testing an existing application that extracts text from PDFs. The application receives a PDF document as an input, extracts all text visible to an end-user (text that would normally be seen upon opening a PDF in any common PDF viewer e.g. Adobe Acrobat Reader) and returns plain UTF-8 data. If the PDF is password-protected and requires the user to enter a password upon opening in a viewer the application detects that and returns adequate error.
This testing plan should allow us to understand if every possible PDF is decoded properly and understand in what exact situation the extraction does not produce the expected data. The testing procedure should take into account all possible cases, for example:
- different versions of PDF standard
- different PDFs features available
- different methods of creating a PDF
- different encodings
- etc.
Provided that the application passes the described test cases it should decode successfully any valid PDF document or return information the file is password-protected.
Whilst this project does not require Test Data to be created, the test plan should include an Addendum that clearly states:
- what test data needs to be created for the plan to work
- guidelines on how to create the test data.
Please include a brief work plan for this task in your response.
Out of scope
The following items are not in the scope of this task:
- writing the extraction application
- providing actual PDF files
- executing any tests
a) Experience writing test plans using a QA testers mindset - what could go wrong, how to break it, how to make it do something that the developer wasn't thinking of when they wrote the software.
b) Experience reading and interpreting detailed file specifications and interpreting beneath the covers how different aspects of the format work, and then conceiving test cases from that.
Job Overview
The purpose of the task is to prepare a detailed plan and test cases for testing an existing application that extracts text from PDFs. The application receives a PDF document as an input, extracts all text visible to an end-user (text that would normally be seen upon opening a PDF in any common PDF viewer e.g. Adobe Acrobat Reader) and returns plain UTF-8 data. If the PDF is password-protected and requires the user to enter a password upon opening in a viewer the application detects that and returns adequate error.
This testing plan should allow us to understand if every possible PDF is decoded properly and understand in what exact situation the extraction does not produce the expected data. The testing procedure should take into account all possible cases, for example:
- different versions of PDF standard
- different PDFs features available
- different methods of creating a PDF
- different encodings
- etc.
Provided that the application passes the described test cases it should decode successfully any valid PDF document or return information the file is password-protected.
Whilst this project does not require Test Data to be created, the test plan should include an Addendum that clearly states:
- what test data needs to be created for the plan to work
- guidelines on how to create the test data.
Please include a brief work plan for this task in your response.
Out of scope
The following items are not in the scope of this task:
- writing the extraction application
- providing actual PDF files
- executing any tests