Hi,
Usually when we test things we create many test_myfeature_foobar.py
, test_myfeature_foobar2.py
and so on to test the code and the coverage.
In my case I use pytest, and we asked me to test the access of customers portal.
So I started with
(yeoboseyo) ✔ ~/Projects/yeoboseyo/yeoboseyo/yeoboseyo [master|✚ 6…11] | |
11:35 $ python app.py | |
여보세요 ! | |
INFO: Started server process [25851] | |
INFO: Waiting for application startup. | |
INFO: Application startup complete. | |
INFO: Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit) | |
#!/usr/bin/env python | |
import asyncio | |
import json | |
import websockets | |
async def hello(): | |
uri = "ws://localhost:8888" | |
async with websockets.connect(uri) as websocket: |
from kivy.lang import Builder | |
from kivy.uix.boxlayout import BoxLayout | |
from kivy.properties import StringProperty, ListProperty | |
from kivymd.app import MDApp | |
from kivymd.theming import ThemableBehavior | |
from kivymd.uix.list import OneLineIconListItem, MDList, OneLineListItem | |
import sqlite3 |
2019-06-21 11:23:23,011 INFO tasks 14493 < TASK [Gathering Facts] > | |
2019-06-21 11:23:23,011 INFO tasks 14493 ------------------------ | |
2019-06-21 11:23:23,011 INFO tasks 14493 \ ^__^ | |
2019-06-21 11:23:23,011 INFO tasks 14493 \ (oo)\_______ | |
2019-06-21 11:23:23,011 INFO tasks 14493 (__)\ )\/\ | |
2019-06-21 11:23:23,011 INFO tasks 14493 ||----w | | |
2019-06-21 11:23:23,012 INFO tasks 14493 || || | |
2019-06-21 11:23:23,012 INFO tasks 14493 |
# coding: utf-8 | |
""" | |
joplin-web sauce starlette | |
""" | |
# starlette | |
from starlette.applications import Starlette | |
from starlette.config import Config | |
from starlette.responses import JSONResponse | |
from starlette.routing import Mount, Route, Router | |
from starlette.staticfiles import StaticFiles |
FROM python:3.6 | |
ENV PYTHONUNBUFFERED 1 | |
RUN mkdir /app/ | |
COPY . /app | |
WORKDIR /app/ | |
RUN apt-get update && apt-get install -y sqlite3 | |
RUN pip install -r requirements.txt |
FROM python:3.6 | |
ENV PYTHONUNBUFFERED 1 | |
RUN mkdir /app/ | |
COPY . /app | |
WORKDIR /app/ | |
RUN apt-get update && apt-get install -y sqlite3 | |
RUN pip install -r requirements.txt |
version: '3' | |
services: | |
frontend: | |
image: foxmask/joplin-web:joplin-front | |
build: | |
context: . | |
dockerfile: Dockerfile-front | |
links: | |
- backend |
<?xml version="1.0" encoding="UTF-8"?> | |
<!DOCTYPE en-export SYSTEM "http://xml.evernote.com/pub/evernote-export2.dtd"> | |
<en-export export-date="20180321T193313Z" application="Evernote/Windows" version="6.x"> | |
<note><title>Le Labyrinthe 3 – L’ennui mortel</title><content><![CDATA[<?xml version="1.0" encoding="UTF-8"?> | |
<!DOCTYPE en-note SYSTEM "http://xml.evernote.com/pub/enml2.dtd"> | |
<en-note><p style="text-align:justify;">Avant de rentrer dans le cœur de notre sujet, il est temps de rappeler quels étaient les résumés des deux précédents volets du <em>Labyrinthe</em>, série de films qui n’a rien à voir avec le jeu de plateau qui fit peut-être les grandes heures de votre enfance.</p><p style="text-align:justify;"><strong>Résumé de l’épisode 1 :</strong> Thomas, un adolescent attardé, se réveille sans mémoire au cœur, c’est fou, d’un labyrinthe en compagnie d’autres gens de son âge. Malgré leur Q.I cumulé de 82, ils décident de suivre Thomas, qui est certes con, mais a le cœur pur, ou autre argument foireux qui exp |