Comments (3)
Read the philosophy behind Test::Inline in the docs.
The idea is to keep tests which are tightly related to a single method as
close to the code as possible so free complete implementation code/test/doc
is all in one place.
It helps me with PPI, where the code is so crazily split out the way it is,
and there has been enormous refactoring in the past.
But I recognise that with additional developer resources this problem goes
away to some extent, so I'm fine with move the tests away from the code if
it well make the test sir les surprising for others.
Adam
On Dec 18, 2013 8:36 AM, "Christian Walde" [email protected] wrote:
I just realized that a whole bunch of test scripts that i need to change
are generated from POD at runtime. Since having code in comments is a
terrible idea, i'd like to extract them and put them into scripts
permanently. Any particular opposition to this?—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12
.
from ppi.
Yeah, i understand the idea, i just find myself very nervous by code in what amounts to comments. It'd be much nicer if it was a test method on the class, called by the .t file.
That said, thanks for not minding a split much. Since it'll be just removing the comments after making sure the test files match them, that shouldn't be tricky.
from ppi.
This has been adressed in #42 and merged into master.
from ppi.
Related Issues (20)
- CHECK bareword handle parsed as scheduled statement HOT 1
- No unknown public methods test failing HOT 1
- Indented here-doc loses whitespace before final delimiter
- provide delimiters for PPI::Token::QuoteLike::{Words,Regexp,Command}, PPI::Token::Quote::{Literal,Interpolate}
- dies with unicode bare key name HOT 1
- use signatures not supported by PPI HOT 1
- Lexical subroutine doesn't return correct name HOT 2
- Misparse bareword as label HOT 7
- Maybe bump minimum Perl version to 5.008?
- try/catch syntax misparsed
- Extending PPI HOT 2
- Parse DSL as a sub HOT 2
- The Keyword Question HOT 20
- Verify behaviour of BEGIN, UNITCHECK, CHECK, INIT and END
- TODO: tidy everything
- TODO: remove superfluous `#pod` lines
- TODO: verify INHERITANCE documentation for all classes
- TODO: auto-generate copyright, author, contributor notices (see strictures.pm)
- TODO: probably un-inline Inlined $self->__add_element(shift);
- TODO: create test cases for the constructs in Syntax::Construct
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ppi.