Skip to content

Instantly share code, notes, and snippets.

@sasezaki
Created April 4, 2012 14:22
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save sasezaki/2301554 to your computer and use it in GitHub Desktop.
Save sasezaki/2301554 to your computer and use it in GitHub Desktop.
comment test
I feel require separating target components into 4 or 5 sets
for "Which component should test?"
[a]. ".travis/new-and-upgrading-components"
- Stdlib, EventManager, Cache, Http, Loader, Log, Mail, Session,
Db , Uri, View
Serializer, Markup,
Module, Mvc & Docbook
[b-1]. ".travis/tested-components" (apply namespace & CS from zf1, not
planned updating for zf2)
- Acl, Barcode, Captcha, Tag, Text, TimeSync, Memory, Measure, Mime,
Json, Server
Cloud, Dojo
Search, Pdf,
InfoCard, Soap, XmlRpc,
File, Filter, Validator,
Debug, Registry & others
-- ZF1 patch sync target
[b-2].".travis/upgrading-related-components"
- Authentication, Paginator, Queue & others (Db related)
- Amf (Code related)
- Wildfire (Mvc related)
-- This is also ZF1 patch sync target(avoid upgrading related)
[c]. ".travis/work-in-progress-components" (marked as skipped)
- Code,
Console, Form, Crypt[?], i18ns (Locale, Date, Currency, Translator),
Feed & OpenId & others
(http://framework.zend.com/wiki/display/ZFDEV2/Development+Status+Page)
[d]. ".travis/planning-shipped-separate"
- Service Components
should be run test target currently?
[a] - Yes
[b-1] - Yes
[b-2] - ?
currently tests will fail.
require upgrading for dependency component upgrading.
But personally I think should be target now.
[c] - No
because current masters's test code is not upgrading for ZF2 yet.
[d] - ? (I don't have any idea)
On the other hand,,
http://packages.zendframework.com/
selected components is packaging.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment