This plugin is a verification “Swiss army knife” helping journalists to save time and be more efficient in their fact-checking and debunking tasks on social networks especially when verifying videos and images.
The provided tools allow you to quickly get contextual information on Facebook and YouTube videos, perform a reverse image search on Google, Baidu or Yandex search engines, to fragment videos from various platforms (Facebook, Instagram, YouTube, Twitter, Daily Motion) into keyframes, to enhance and explore keyframes and images through a magnifying lens, to query Twitter more efficiently through time intervals and many other filters, to read video and image metadata, and to apply forensic filters on still images.
For further details about the tool and the already released versions, please visit the plugin page on our latest project website.
For any feedback (bugs, enhancement, suggestions), please use the feedback tool within the plugin (on the bottom right) or file an issue on GitHub.
This plugin was initially developed by the InVID European project (2016-2018), a Horizon 2020 Innovation Action funded by the European Union under Grant Agreement 687786. It has been enhanced by the WeVerify European project (2018-2021), a Horizon 2020 Innovation Action funded by the European Union under Grant Agreement 825297. Since September 2022, it is improved within the vera.ai project under Grant Agreement 101070093.
For more information about those three projects, visit the vera.ai website, the WeVerify website, and InVID website or follow us on veraai_eu, InVID_EU or on WeVerify.
Disclaimer: This software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and non-infringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software.
The Verification plugin is a browser based plugin built with React and Redux.
To install the dependencies run
npm installor
yarn installAdd an .env file at the root containing
REACT_APP_KEYFRAME_API=<keyframe_url>
REACT_APP_MY_WEB_HOOK_URL=<slack_webhook_url>
REACT_APP_TRANSLATION_URL=<translation_server_url>
REACT_APP_TRANSLATION_TAG=<The current translation tag, e.g. v0.83>
REACT_APP_TSNA_SERVER=<tsna_url>
REACT_APP_ASSISTANT_URL=<assistant_url>
REACT_APP_DBKF_SEARCH_API=<dbkf_url>
REACT_APP_DBKF_SIMILARITY_API=<dbkf_similarity_url>
REACT_APP_BASEURL=<baseurl>
REACT_APP_CAA_FORENSICS_URL=<forensics_url>
REACT_APP_CAA_ANALYSIS_URL=<analysis_url>
REACT_APP_CAA_ENVISU4_UTILS_URL=<envisu4_url>
REACT_APP_CAA_DEEPFAKE_URL=<deepfake_url>
REACT_APP_CAA_LOCATION_URL=<location_url>
REACT_APP_MATOMO_URL=<matomo_url>
REACT_APP_MATOMO_DOMAIN=<matomo_domain>
MATOMO_SITE=<matomo_site>
REACT_APP_VIDEORIGHT_API=<videoright_url>
REACT_APP_LOCCUS_URL=<loccus_url>
REACT_APP_AFP_REVERSE_SEARCH_URL=<reversesearch_url>
REACT_APP_SEMANTIC_SEARCH_URL=<semanticsearch_url>
ARCHIVE_BACKEND=<archive_url>Run the dev script to build the React app in development mode
npm run devRun the build to build the React app for production
npm run build Chrome for Developers documentation
build folder).The playwright framework is used for e2e, component and unit testing. All tests are located
in the tests folder with the following structure:
tests
!- component_unit - Component and unit testing
|- e2e - End to end testing
-- examples - Examples to serve as a reference only
Note: Before running all (or just e2e) tests, the extension must first be built. See End-to-end (e2e) testing section for more details
All tests (e2e, component & unit) can be run using the command:
npm run test
Component and unit testing are run together using the following command:
npm run test-cu
Playwright configurations of the component and unit tests can be found in /playwright-ct.config.js
Component and unit testing uses the
experimental playwright component testing module.
When running tests, the browser loads the page in ./playwright/index.html and any resources
in ./playwright/index.jsx.
Tests can then mount a component directly on the page and run tests similar to e2e testing.
Transpiling and bundling of assets are done on the fly using vitejs instead
of webpack.
Note: Component testing is best done on components that can be easily isolated. Ones that rely on redux or routing are likely to be more suitable for e2e testing.
Note: Playwright/vite generates cache files at /playwright/.cache which sometimes does not get updated properly
when .jsx files changes, so currently the command npm run test-cu deletes the cache directory before running the
tests.
E2E testing can be run using the following command:
npm run test-e2e
Playwright configurations of the e2e tests can be found in /playwright.config.ts.
Before running all (or just e2e) tests, the extension must first be built using npm run build.
The compiled WeVerify extension in the ./build directory can be loaded into the browser by using the fixture code in
/tests/e2e/fixtures.ts. All e2e tests of the extension should import the overridden test and expect functions in
the fixtures.ts file.
The overridden test function provides an additional extensionId variable in the handler function which is
needed to navigate to the location of the extension.
The following code shows how we can navigate to the root page of the extension:
import {test, expect} from './fixtures';
test('Example extension test', async ({page, extensionId}) => {
// Navigates to the root page of the plugin
await page.goto(`chrome-extension://${extensionId}/popup.html`);
// ... test whatever functions
});UI mode is for e2e test can be run using:
npm run test-e2e-uiThis will open a browser with interactive testing environment which can be useful for debugging.