# QA Intro This section is a list of QA steps to go through before each release. To be keep up to date with changes of each new release. Here is a video demo of the main "Transcription" in v `1.0.5` use case: . Needs to be updated with v`1.0.6` paper-editing. But still relevant for transcription part. The app should be downloaded on a mac OS X that does not have any [dependencies installed on the system, e.g. node, ffmpeg, etc... see here for full list](broken://pages/-LKESYLCZkVCyfYSvjbe). Here is the [latest release](https://github.com/OpenNewsLabs/autoEdit_2/releases). For any issues during the QA process please file in the [Github repo](https://github.com/OpenNewsLabs/autoEdit_2) and assign to `pietrop`, tag them as `QA` and the version number eg `1.0.6`. See [user manual](https://pietropassarelli.gitbooks.io/autoedit2-user-manual/content/transcribing.html) along side QA notes for visual representation of each state. ## Earlier version [Google doc: **QA Test Plan autoEdit 2,** 29th March 2017 ](https://docs.google.com/document/d/18hqjb5K7owSV6HJ-uqgeFwxicRUvf-nYsdpJiBkF-BU/edit?usp=sharing) {% embed url="" %} ## --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://autoedit.gitbook.io/documentation/master-1.0.13-1/qa-list/qa-intro.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.