Skip to content

Instantly share code, notes, and snippets.

flow2k

Block or report user

Report or block flow2k

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@tasdikrahman
tasdikrahman / python_tests_dir_structure.md
Last active Aug 29, 2019
Typical Directory structure for python tests
View python_tests_dir_structure.md

A Typical directory structure for running tests using unittest

Ref : stackoverflow

The best solution in my opinion is to use the unittest [command line interface][1] which will add the directory to the sys.path so you don't have to (done in the TestLoader class).

For example for a directory structure like this:

new_project
├── antigravity.py
@dcunited001
dcunited001 / new_finder_window.applescript
Created Dec 2, 2012
Automator Service to Open New Finder Window
View new_finder_window.applescript
-- create new service in automator
-- set input to "no input" instead of "text"
-- add new task: run applescript
on run {input, parameters}
tell application "Finder"
activate
set new_window to make new Finder window
end tell
end run
You can’t perform that action at this time.