Use a custom oauth token so we can predict and validate the client_name and website

This commit is contained in:
Mark Felder 2021-02-11 15:53:10 -06:00
parent 4b979538bc
commit bd3d0e8b57
1 changed files with 12 additions and 3 deletions

View File

@ -358,7 +358,16 @@ test "posting a direct status", %{conn: conn} do
assert activity.data["cc"] == [] assert activity.data["cc"] == []
end end
test "preserves client application metadata", %{conn: conn} do test "preserves client application metadata" do
%{user: _user, token: token, conn: conn} = oauth_access(["write:statuses"])
%Pleroma.Web.OAuth.Token{
app: %Pleroma.Web.OAuth.App{
client_name: _app_name,
website: _app_website
}
} = token
result = result =
conn conn
|> put_req_header("content-type", "application/json") |> put_req_header("content-type", "application/json")
@ -369,8 +378,8 @@ test "preserves client application metadata", %{conn: conn} do
assert %{ assert %{
"content" => "cofe is my copilot", "content" => "cofe is my copilot",
"application" => %{ "application" => %{
"name" => "Some client 0", "name" => app_name,
"website" => "https://example.com" "website" => app_website
} }
} = json_response_and_validate_schema(result, 200) } = json_response_and_validate_schema(result, 200)
end end