sillsdev / sillsdev/languageforge-lexbox

Setup e2e tests with FW Lite against staging

Open
#1,824 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

💻 FW Lite testing
Dominant language
C#
Stars
9
Forks
8
Avg merge
2d 13h
Merged PRs (30d)
49

Description

Right now we don't have any e2e tests with FW Lite running and connecting to lexbox, downloading a project making changes etc.

In order to avoid breaking important stuff like media files, or live sync, we need to write some tests. These should be similar to our S&R tests, where we can configure the server they run against, but they have some built in expectations of the projects and users that will be available.

First test case I'd like to cover:

  1. Launch FW Lite, download a project (sena-3?)
  2. Create a new entry via the UI
  3. Delete local project copy
  4. Download the same project again
  5. Find the entry previously created

This will cover a wide range of features, login, download, auto sync. Once we've got a first test setup we can build out more in the future.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the existing S&R tests and how they configure the server they run against. Set up an FW Lite end-to-end test against staging that downloads the specified project, creates an entry through the UI, deletes the local copy, downloads it again, and verifies the entry remains available.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.