Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Give reasons why to migrate to alsatian #158

Closed
jamesadarich opened this issue Sep 20, 2016 · 0 comments · Fixed by #187
Closed

Give reasons why to migrate to alsatian #158

jamesadarich opened this issue Sep 20, 2016 · 0 comments · Fixed by #187
Assignees
@jamesadarich
Labels
documentation
Milestone
beta.1

Comments

@jamesadarich
Copy link
Member

Alsatian is great but we need to tell people WHY to move

key points:

  • no globals
  • smaller, simpler specs - largely due to decorators namely @TestCase
  • outputs TAP
  • gives you as many hints as possible (throws clear errors when things aren't set up quite right)
  • code base is excellent quality (see badges) and 100% covered in tests (written in Alsatian don't you know)
  • written in TypeScript for TypeScript
@jamesadarich jamesadarich modified the milestone: beta.1 Sep 21, 2016
@jamesadarich jamesadarich self-assigned this Oct 19, 2016
@jamesadarich jamesadarich mentioned this issue Oct 20, 2016
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jamesadarich jamesadarich

Labels
documentation
Projects
None yet
Milestone
beta.1
Development

Successfully merging a pull request may close this issue.

Issue#158 jamesadarich/alsatian
1 participant
@jamesadarich