[DRE-maint] Bug#797972: add sprockets tests for rails engines

[Pirate Praveen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Friday 04 September 2015 05:47 PM, Antonio Terceiro wrote:
> On Fri, Sep 04, 2015 at 10:18:15AM +0530, Pirate Praveen wrote:
>> package: gem2deb version: 0.20.2 severity: wishlist
>> 
>> A simple test like this can test if the asset is installed
>> correctly
>> 
>> rails new foo cd foo echo "//= require asset >>
>> app/assets/javascripts/application.js bundle exec rake
>> assets:precompile
> 
> you can use sprockets directly instead of a full rails app. check 
> debian/tests/smoke-test in ruby-bootstrap-sass for an example.

ok. Can you pass a javascript file sprockets?

>> there should be an option --check-assets to gem2deb test runner
>> and if the gem name starts with rails-assets or ends with rails
>> it should be enabled by default.
> 
> assuming that deriving the asset name from the package name will 
> actually work, there are also quite a few details to get right,
> such as adding the necessary build dependencies, and handling the
> paths when running during build vs running on autopkgtest (and thus
> with the package already instaled) etc.
> 

There has to be an automated test and autopkgtest is also fine. If
app/assets or vendor/assets are found, we should add such tests with
gem2deb.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJV6rmpAAoJEM4fnGdFEsIqiK8P/2Gowh3iwvBKExhh61c2YaY4
hl/FdYecfwWLrgPdI2K/tQDqsHOBzkjBC7e/JePqL5eB8/8cW0ZEph1Fz4yO7Qxv
pcQdGLyPSq7ctl6fbVoLw4UMQykvZU1MJChURRvC6oblAE0pWA7BRdDyhl04aMEW
rYvUA3IIDlzRq8UmibgDtlc925GhwshjH1rZup/TvhSD39eantiwYEDriTHCh78y
Q5bgqe3bwVe/+gMKSH/0sXv10s3/eTlQIKb8gWpKE68naR9oNYDC4SoIURjh+xpP
u8mnWs+BkhlH9rrm3cXrv6VDT9ifR59SbPnlIu1I/ODirT8XEXqFVZ1vsByHITxw
jItgMsFL50H/tbASf6jQxhPwkNvmm1eOiVGILWiDuRPUA52bR2eJymlRoomRfcrJ
Dli3YDgLrV5z6uwIs0NKuUkcgkUasAtTVkDTIDwr6M8mXpmLFfNDD7qdidfaS5xQ
0Y2r9jbzRJLMcP3ABl6PAZpJVJrd1Q2E834lKdQjTAcXvKZ/tLWovEDUICndZlzW
f8xZAQA6Zx3EHwoImlR5MS3Jli1gPWCYqMMSfKO4axmZofCEr6U/37/pTIsdZZ0B
QKqR988pvnftLHUzbZjrmwkcge1uQiMbNeMl3nBkobU+jOJ22JDR4L66JO6SC14N
Avn6eC3Ywoc7kd6UKUUe
=4xje
-----END PGP SIGNATURE-----