1
edit
Changes
→Project Leader(s)
[[user:Evmarbella|Ezadkiel Villarico Marbella]]
[http://zadkielm.blogspot.com/search/label/reftest Project Blog]Up-To-Date Information [http://zadkielm.blogspot.com/2008/10/pixel-reftesting-with-profiles.html Colour Profile Reftest 0.1] Gained basic knowledge of reftesting with colour profiles [http://zadkielm.blogspot.com/2008/11/colour-profile-reftest-02and-then-there.html Colour Profile Reftest 0.2] Created tests and filed bugs [http://zadkielm.blogspot.com/2008/12/reftest-03-manifesting-bug-459617.html Colour Profile Reftest 0.3] Research on tracking down bug and test manifests
== Project Contributor(s) ==
NOTE: only Project Leader(s) should add names here. You '''can’t''' add your own name to the Contributor list.
If anything is unclear feel free to edit the instructions or msg me on IRC or email me.
Instruction <br />
notes from: <br />
http://zadkielm.blogspot.com/2008/09/firefox-and-reference-testing-reftest.html <br />
http://zadkielm.blogspot.com/search/label/reftest <br />
1 <br />
Have a build of firefox on the linux with <br />
ac_add_options --enable-tests <br />
on the mozconfig <br />
2 <br />
download the reftest <br />
[http://zenit.senecac.on.ca/wiki/imgs/Pngsuite-colorprofiles-failedtest-contrib.zip contrib-failedtest] <br />
unzip it in your home folder.<br />
open terminal<br />
and <br />
cd ~/pngsuite-colorprofiles-failedtest<br />
run the reftest <br />
~/pngsuite-colorprofiles$ ~/src/obj*/dist/bin/firefox --no-remote -reftest -P testfirefox1(replace with test Profile) ./failedPixelTestAdobe1998.list | grep REFTEST > failedPixeltestAdobe1998output(insert Linux OS).txt
3<br />
open the failedPixelAdobe1998output*.txt<br />
Outcome:<br />
It should failed and it should have <br />
the URI data of the tested pixels/images.<br />
see <br />
'fail line output' <br />
http://zadkielm.blogspot.com/2008/09/reftesting-testing-continues.html <br />
Upload the text file on the zenit wiki <br />
(failedPixeltestAdobe1998output(insert Linux OS).txt ) <br />
Please include your Processor/OS information. <br />
ex. <br />
Processor Speed and Brand..., <br />
Version of Linux. <br />
and add your name on the contributions. <br />
'''Please post your test results here:'''
{| border="1"
|-
! Date
! IRC Nick
! Platform
! Firefox Version
! Processor
! Result
|-
| 19-Oct-2008
| ezadkiel
| Ubuntu Release 8.04(hardy) Kernel Linux 2.6.24-19-generic GNOME 2.22.3
| Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b2pre) Gecko/20081019 Minefield/3.1b2pre
| Intel Core 2 CPU T7400 @ 2.16 GHz
| it passed [http://zenit.senecac.on.ca/wiki/imgs/FailedPixeltestAdobe1998outputUbuntu.txt.zip test-result]
|-
|}
== Project Details ==
Photoshop does it. Preview in Mac OSX does it which means
you can use Automator to apply profiles on multiple images
'''Technote005:'''
reftest can compare images now output is sRGB if the reftest fails
'''Technote007:''' Use URI scheme for reftest [http://en.wikipedia.org/wiki/Data:_URI_scheme DATA URI Scheme Wiki]
simple to complex > back to simple
bug 459617 details
https://bugzilla.mozilla.org/show_bug.cgi?id=459617
- first figure out the exact pixel that's different
- then add some conditional code in cmsDoTransform that checks for that pixel, prints it on input, and prints the transformed pixel
-and see if you can confirm that the issue is within LCMS, or whether it's actually somewhere else
-if it's an LCMS issue if you can get the lcms code to say that it's outputting different pixels on different platforms for the same input pixel and transform
== Project News ==
simplified reftest to show failing pixel and reftest differences in GIMP
- Oct 12/08
filed a bug
[https://bugzilla.mozilla.org/show_bug.cgi?id=459617 bug#459617]
trying to narrow it down.
- Oct 19/08
how to test in different configurations.
- Nov 9/08
updating the test...it's too [http://zadkielm.blogspot.com/2008/11/hg-add-to-patches.html big]
- Nov 24/08
learning about hg queues
adding and importing folders and files patches.
looking at [https://bugzilla.mozilla.org/show_bug.cgi?id=463221 bug] comments particularly:
Yay, reftests!
A few tiny drive-by nits:
"pngsuite" is actually an official PNG test suite, so these should go under a
different name. Say, modules/libpr0n/test/reftest/png/color-profile/.
A single reftest.list manifest is fine, no need to break it into small chunks.
The readme could just be distilled down into plain test, and rolled into the
manifest as brief comments.
