Self-hosted service
TechXueXi/TechXueXi avatar
TechXueXi/TechXueXi

TechXueXi: a Selenium runner for Xuexi quizzes, pinned to Chrome 92

TechXueXi: the most useful open-source web assistant for Xuexi Qiangguo (Study the Great Nation), an automated, lazy-friendly scoring tool that supports quiz answering and Docker deployment, earning up to 45 points per day.

5,699 stars1,871 forksPythonLGPL-3.0

At a glance

What is it?
TechXueXi drives the daily, weekly and topic quizzes of the Xuexi Qiangguo study app through a real Chrome window, either from a local Python install or the published Docker image. The automation is straightforward, but the packaging is dated, since the image carries Chrome 92 on Python 3.7 and the project warns against running it on a VPS.
Who is it for?
Adopt TechXueXi only if you have a personal machine with a graphical session, a chromedriver matching your own Chrome, and no problem with a project whose README says the maintainers may delete the repository at any time.
Can I use it commercially?
Yes, with conditions. LGPL-3.0 is a weak copyleft licence: you can use it inside commercial and closed-source software, but if you distribute changes to its own files, you must publish those changes under the same licence.
Is it still maintained?
Activity is slowing. The repository last received commits 7 months ago.
What is it written in?
Mainly Python, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • TechXueXi/TechXueXi5,699 ★ · +33
Star history
Repository2026-09-232026-11-15
TechXueXi/TechXueXi5.7k5.7k

33 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Selenium answers the quiz through a real Chrome window

Every action TechXueXi takes happens inside a browser it drives. The dependency list pins selenium==3.141.0 next to requests==2.26.0, lxml==4.6.5 and beautifulsoup4==4.9.3. Three quiz types are covered: the daily set, the weekly set, and the topic quizzes that the compose file switches on with ZhuanXiang=True. Multithreading is the default and can be turned off; the project puts a full day of points at about 20 minutes of running. The browser can stay hidden while the run continues, or you can enable the foreground display, and a separate pass keeps re-reading the score page until the day's number is reached.

text
selenium==3.141.0
requests==2.26.0
lxml==4.6.5
beautifulsoup4==4.9.3
pyhocon==0.3.58

Those five pins are part of a longer committed list of 17 entries that also includes pyzbar, Flask, qrcode and pyTelegramBotAPI. pyhocon is the configuration reader that loads the settings files, and Pillow>=9.0.1 is the only entry left unpinned.

Chrome 92 and a 2021 chromedriver decide what your machine can run

The image pins a browser pair from 2021, installs Chrome from a .deb package, then fetches the driver that goes with it:

dockerfile
RUN cd /xuexi/; \
  wget -O chromedriver_linux64_92.0.4515.107.zip http://npm.taobao.org/mirrors/chromedriver/92.0.4515.107/chromedriver_linux64.zip; \
  unzip chromedriver_linux64_92.0.4515.107.zip; \
  chmod 755 chromedriver; \
  ls -la; \
  ./chromedriver --version

The layer above it installs google-chrome-stable_92.0.4515.159, and a chromedriver only drives the Chrome generation it was built for. Inside the image the pair is consistent. On a desktop that already carries a current Chrome it is not, and the repository ships no script that fetches a matching driver for you. The base image is python:3.7-slim, and the apt line adds wget, unzip, libzbar0, git, cron and supervisor with TZ set to Asia/Shanghai. libzbar0 is the native half of pyzbar==0.1.8, the barcode and QR decoder sitting in the same requirements list.

docker-compose.yaml is the whole install recipe: port 9980 and a cron entry

There is no installer script in this repository, and the README sends download and usage questions to the wiki page 使用方法-更新方法-下载方式.md. The deployment recipe that does ship is docker-compose.yaml, and its service definition is this:

yaml
    image: techxuexi/techxuexi-amd64
    container_name: techxuexi
    restart: unless-stopped
    volumes:
        - ./xuexi:/xuexi/user
    ports:
        - 9980:80
    shm_size: 2gb
    environment:
        - CRONTIME=5 */6 * * *
        - Pushmode=6
        - ZhuanXiang=True

Start that service and the file's own comment tells you what to do next: open IP:9980. Four settings decide what happens afterwards. CRONTIME is a cron expression, 5 */6 * * * in the compose file against the Dockerfile default of 30 9 * * *, so the container wakes every six hours rather than once at 09:30. ZhuanXiang=True turns the topic quizzes on. Pushmode is 6 in the compose file and 1 as the Dockerfile default, and the Dockerfile also declares empty AccessToken and Secret variables. shm_size: 2gb is there because Chrome needs shared memory, and the ./xuexi bind mount keeps your account and config data outside the container.

The setup the project tells you to avoid is the VPS

The project's own advice is to keep this off shared hosting: use a machine with a graphical session, prefer Windows, use your own computer, and stay off VPS and cloud instances, because the study service can identify an account from the IP range of its provider. Windows XP is out. Raspberry Pi is in, at least at the build level: Dockerfile_arm32v7 and Dockerfile_arm64v8 sit next to their .dev variants, with docker-manifest.sh and docker-build-dev.sh to assemble them. Support runs through the repository itself, and issue 14 carries the chat group. Announcements are split across two addresses because one of them is unreachable from inside China: t.me/s/techxuexi_notice and notice.techxuexi.workers.dev. Worth weighing before you depend on any of it: the README states plainly that the maintainers may delete the repository at any time and asks you to join the group so you can be reached.

Commits land on developing while the newest release tag sits in 2022

The last push to this repository was on 2026-03-27, and the three most recent releases are v20220126 from 2022-02-03, v20211221 from 2022-01-14 and v20211103 from 2021-11-08. So the branch moves and the tags do not: cloning developing gets you code from March 2026, while anyone tracking releases holds a 2022 build. The default branch is developing, though the Dockerfile build argument defaults to usebranche="dev", and the compose file shows how a build can be redirected with the Sourcepath and pullbranche lines, both left commented out. Contribution rules point at the same branch: changes go only into developing until the item is marked Done on the roadmap board at github.com/orgs/TechXueXi/projects/2, which only team members can open, and membership is requested through issue 2. On Windows the update path is a batch file, windows系统git_pull_一键更新.bat, and the tree also carries a post-update entry.

The struck-through lines are the features it will not have

Two entries in the feature list are struck through, and they are the two a long unattended run would want. Saving account information so you skip the daily login is gone. So is the automatic shutdown after the day's work is done. The scope narrows in the same way elsewhere: Android is not a package but a note pointing at issue 323, marked as possibly unusable. Nothing here covers what happens when the quiz page changes its markup, and there is no documented rollback for a bad update. Treat 45 points a day as the ceiling the project advertises, not a promise per account.

A published amd64 image, a local Python install, or doing it by hand

Three routes, three different prices. The published image is the cheapest to start: techxuexi/techxuexi-amd64 already contains Chrome, the chromedriver, cron and the Python dependencies, and the cost is that it carries 2021 browser binaries on Python 3.7. A local install gives you a current browser, but you supply the matching chromedriver yourself, and on Windows you may hit a missing api-ms-win-crt-runtime-l1-1-0.dll entry point, for which the README points at Visual C++ Redistributable for Visual Studio 2015, hosted in a separate VC-REDIST repository. The third route installs nothing: the official app and its quizzes, done by hand. That is the option the README itself recommends, describing the app as free reading (journals, ancient texts, open courses, songs, opera, films) and saying TechXueXi is only meant for non-programmers too busy with work or study to finish the tasks. One more alternative is not on the table, because the project says it grew out of a predecessor that has ended and never names it, leaving no upstream to compare against or fall back to.

Editorial conclusion

Adopt TechXueXi only if you have a personal machine with a graphical session, a chromedriver matching your own Chrome, and no problem with a project whose README says the maintainers may delete the repository at any time. Skip it if your only host is a VPS or a cloud instance, if you need stored credentials (that feature is struck out of the feature list), or if you need a release line rather than a branch, since the newest tag is v20220126 from 2022-02-03 while the last push landed on 2026-03-27. Verify first that the pinned pair, google-chrome-stable_92.0.4515.159 with chromedriver 92.0.4515.107, still completes one quiz against the current site before you build anything on top of it.

Frequently asked questions

What does TechXueXi automate inside the Xuexi Qiangguo app?

It drives a real Chrome with Selenium and works through the daily, weekly and topic quizzes, then re-reads the score page until the day's target is reached. The project advertises up to 45 points a day and about 20 minutes of running with multithreading on.

Where do I get TechXueXi, and can it run on a Raspberry Pi or a VPS?

Download and usage steps live in the wiki page 使用方法-更新方法-下载方式.md, and the repository ships DOCKER.md, docker-compose.yaml and Dockerfiles for arm32 and arm64. Raspbian-pi is on the supported list, while VPS and cloud hosts are the one setup the README tells you to avoid, because the service can be identified by the provider's IP.

Why does TechXueXi fail on Windows with a missing ucrtbase DLL?

The README records a Windows failure where ucrtbase.terminate cannot be located in api-ms-win-crt-runtime-l1-1-0.dll. It points at Visual C++ Redistributable for Visual Studio 2015, with vc_redist.x64.exe and vc_redist.x86.exe linked from a separate VC-REDIST repository.

Can I use TechXueXi for commercial work?

The code is under LGPL-3.0, while the README's own disclaimer bans commercial use and any profit-making activity and says the project accepts no donations. The disclaimer adds a condition the license text does not spell out, and the README does not say how the two are meant to interact.

Official sources

  1. License: LGPL-3.0
  2. Project website
  3. README
  4. Releases
  5. TechXueXi/TechXueXi on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/techxuexi-techxuexi.svg)](https://hysenlabs.com/projects/techxuexi-techxuexi)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/techxuexi-techxuexi.svg)](https://hysenlabs.com/projects/techxuexi-techxuexi)

Was this useful?