##// END OF EJS Templates
git: use force fetch and update for target ref. This solves a case...
git: use force fetch and update for target ref. This solves a case when in PRs a target is force updated and is out of sync. Before we used a pull which --ff-only fails obviosly because two are out of sync. This change uses new logic that resets the target branch according to the source target branch allowing smooth merge simulation.

File last commit:

r2487:fcee5614 default
r2784:e8c62649 default
Show More
test_db_manage.py
92 lines | 3.0 KiB | text/x-python | PythonLexer
# -*- coding: utf-8 -*-
# Copyright (C) 2010-2018 RhodeCode GmbH
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU Affero General Public License, version 3
# (only), as published by the Free Software Foundation.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU Affero General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
#
# This program is dual-licensed. If you wish to learn more about the
# RhodeCode Enterprise Edition, including its added features, Support services,
# and proprietary license terms, please see https://rhodecode.com/licenses/
import mock
import pytest
from rhodecode.lib.db_manage import DbManage
from rhodecode.model import db
@pytest.fixture
def db_manage(baseapp):
db_manage = DbManage(
log_sql=True, dbconf='fake', root='fake', tests=False,
cli_args={}, SESSION=db.Session())
return db_manage
@pytest.fixture(autouse=True)
def session_rollback(baseapp, request):
"""
Rollback the database session after the test run.
Intended usage is for tests wich mess with the database but don't
commit. In this case a rollback after the test run will leave the database
in a clean state.
This is still a workaround until we find a way to isolate the tests better
from each other.
"""
@request.addfinalizer
def cleanup():
db.Session().rollback()
def test_create_admin_and_prompt_uses_getpass(db_manage):
db_manage.cli_args = {
'username': 'test',
'email': 'test@example.com'}
with mock.patch('getpass.getpass', return_value='password') as getpass:
db_manage.create_admin_and_prompt()
assert getpass.called
def test_create_admin_and_prompt_sets_the_api_key(db_manage):
db_manage.cli_args = {
'username': 'test',
'password': 'testpassword',
'email': 'test@example.com',
'api_key': 'testkey'}
with mock.patch.object(db_manage, 'create_user') as create_user:
db_manage.create_admin_and_prompt()
assert create_user.call_args[1]['api_key'] == 'testkey'
@pytest.mark.parametrize('add_keys', [True, False])
def test_create_user_sets_the_api_key(db_manage, add_keys):
username = 'test_add_keys_{}'.format(add_keys)
db_manage.create_user(
username, 'testpassword', 'test@example.com',
api_key=add_keys)
user = db.User.get_by_username(username)
if add_keys:
assert 2 == len(user.auth_tokens)
else:
# only feed token
assert 1 == len(user.auth_tokens)
def test_create_user_without_api_key(db_manage):
db_manage.create_user('test', 'testpassword', 'test@example.com')
user = db.User.get_by_username('test')
assert user.api_key is None