Skip to content

Instantly share code, notes, and snippets.

View sebastiandero's full-sized avatar
👋

Sebastian De Ro sebastiandero

👋
View GitHub Profile
@sebastiandero
sebastiandero / autoexec.cfg
Last active June 20, 2024 21:17
Autoexec.cfg for CS:GO
//~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--~~--
//
//.----------------. .----------------. .----------------. .----------------. .----------------. .----------------. .----------------.
//| .--------------. || .--------------. || .--------------. || .--------------. || .--------------. || .--------------. || .--------------. |
//| | ________ | || | _________ | || | ____ ____ | || | _________ | || | ____ ____ | || | _ | || | _______ | |
//| | |_ ___ `. | || | |_ ___ | | || ||_ _| |_ _| | || | |_ ___ | | || | |_ _||_ _| | || | | | | || | / ___ | | |
//| | | | `. \ | || | | |_ \_| | || | \ \ / / | || | | |_ \_| | || | \ \ / / | || | \_| | || | | (__ \_| | |
//| | | | | | | || | | _| _ | || | \ \ / / | || | | _| _ | || | > `' < | || | | || | '.___`-. | |
//| | _| |___.'
@sebastiandero
sebastiandero / setup_gotv.cfg
Created March 8, 2017 11:21
GOTV setup config for CS:GO
echo "started DeVeX's GOTV Configuration"
tv_port "27020" //The port GOTV will be reachable
tv_enable "1" //enables GOTV
tv_deltacache "2" //makes everything smoother
tv_delay "0" //change to the seconds of delay you want
tv_snapshotrate "16" //change from 16 - 32 - 64 - 128 tick
tv_password "peratv" // GOTV password
tv_timeout "3" // The time in seconds before server timeout reached
tv_title "peRa Sports Competitive GOTV" //GOTV title
@sebastiandero
sebastiandero / 1v1.cfg
Created March 8, 2017 15:24
1v1 config for CSGO
bot_kick;
exec gamemode_competitive;
mp_free_armor 1;
mp_freezetime 3;
mp_weapons_allow_map_placed 1;
mp_humanteam any;
mp_restartgame 1;
mp_round_restart_delay 3;
mp_roundtime 80250;
mp_maxrounds 30;
@sebastiandero
sebastiandero / core_warmup.cfg
Created March 8, 2017 15:25
Warmup config by CORE for CSGO
///CORE Haven Bot Deathmatch
sv_cheats 1
//Bots
bot_chatter "off"
bot_defer_to_human_items "1"
bot_defer_to_human_goals "1"
bot_difficulty "3"
bot_dont_shoot "1"
@sebastiandero
sebastiandero / testing.md
Last active November 2, 2021 19:16
Coding Guidelines

Testing

At <...>, we practice Test Driven Development. We expect you to write a test before you start working on a piece of functionality. We want at least one test for every small piece of functionality that you write.

Tipps

  • Do not write tests for functions or methods, write tests for functionality
  • In a unit test you should be testing one unit of functionality, not a class or function. If you need 3 classes or functions to write a meaningful test for the functionality, then that's your unit.
  • Use the lowest class of test you can, and the highest you have to: Unit → Integration → E2E. High test classes (for example E2E) help you test functionality instead of writing coverage tests. (high mock count, duplicated implementation, has to be adapted every time you change the functionality)