Re: [Bitcoin-development] 0.7.1 release candidate 1 ready for testing
I'd emailed steve last week to try and get a look at the test cases and such he worked up, but I've not heard from him. Other then that, I'll grab the RC tonight and go through it. Arklan -- As long as there is light, the darkness holds no fear. And yet, even in the deepest black, there is life. - Arklan Uth Oslin I want to leave this world the same way I came into it: backwards and on fire. - Arklan Uth Oslin On Thu, Oct 11, 2012 at 9:59 AM, Jeff Garzik jgar...@exmulti.com wrote: On Thu, Oct 11, 2012 at 11:46 AM, Gavin Andresen gavinandre...@gmail.com wrote: Any progress on a release candidate QA sanity testing plan? Posted a call for testing in this forum thread, https://bitcointalk.org/index.php?topic=117487.0 -- Jeff Garzik exMULTI, Inc. jgar...@exmulti.com -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] 0.7.1 release candidate 1 ready for testing
i'll second the bitcoin test list.
Arklan
--
As long as there is light, the darkness holds no fear. And yet, even in the
deepest black, there is life. - Arklan Uth Oslin
I want to leave this world the same way I came into it: backwards and on
fire. - Arklan Uth Oslin
On Thu, Oct 11, 2012 at 11:45 AM, steve st...@mistfpga.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 11/10/2012 16:46, Gavin Andresen wrote:
Any progress on a release candidate QA sanity testing plan?
essentially yes - in all seriousness, I have come around to your way
of thinking, it is not worth arguing about. we end up in the same place.
:) nothing is final though. I will be opening it up to Arklan in a bit
(I have a pool match tonight so after that depending on how drunk i
get.) and to another couple of people who have emailed me off list who
would like to be involved in testing.
I have not created any new tests for the new stuff. this is still the
noddy stuff.
It covers everything that needs to be covered for a newbe or someone
upgrading clients.
and it is in many formats the moment (from wiki to test runner) none
particularly useful (about to import into mantis, just fiddling with
the fields so it does testcases)
I have been trying to separate the tests into what can be automated,
recorded and checked by watching the video and have sanity checks
along the way (published sha and sha256 of the binaries match) -
(obviously the test is flagged to be run manually if there is any doubt)
I did take myself outside and had a little sit down and talk to
myself. Lets not run before we can walk. I will still keep the grand
ideas, but they are on the back burner. (I got called a blue skies
thinker today, wtf is one of them? I said smiled and said thanks)
the main things we make sure we get tested right are all the GAT tests
in bettermeans.They are more protocol based and should be run against
all releases. Lets nail that process, peer review it, retest it, then
use that as a basis for The Process. I will temper my zealousness. I
realise that I can come across as bullish or even aggressive in my
emails. I never mean too.(unless I say I am. That is not an excuse
for my poor english language skills.)
But I still think that the people running the tests should have the
greatest say in what software is used. So once you have access to the
server and the cases feel free to install your favourite software and
see what other people think.
but we have a vague structure and workflow so it will be interesting
to see how it works out.
the git integration will be trivial.
please email me if you would like access. I am off out in 15 mins but
I promise to have all access sorted by tomorrow. I am only using 3
vps to show example testing and test platforms. I would like it if we
could get a technet license with the donations so far, I use mine (and
my msdn) for work.
also check out bettermeans for the formats that I will be using.
bollocks. bollocks. bollocks
https://secure.bettermeans.com/projects/4180
bye bye bettermeans. how we never knew ye.
Gavin, can we get a bitcoin-test mailing list please. it would be
used for discussion of testing, tools, ideas, chatter, etc. it would
not be a place reporting bugs... This list seems very focused and I
always feel like I am disrupting things with my emails about test. I
dont mind admining the list. I would rather be vocal and inclusive, I
dont think the dev list is the place for that.
Bitcoin version 0.7.1 release candidate 1 is now available from:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.7.1/test/
This is a bug-fix minor release.
New features
* Added a boolean argument to the RPC 'stop' command, if true sets
-detachdb to create standalone database .dat files before shutting
down.
* -salvagewallet command-line option, which moves any existing
wallet.dat to wallet.{timestamp}.dat and then attempts to salvage
public/private keys and master encryption keys (if the wallet is
encrypted) into a new wallet.dat. This should only be used if your
wallet becomes corrupted, and is not intended to replace regular
wallet backups.
* Import $DataDir/bootstrap.dat automatically, if it exists.
Dependency changes --
* Qt 4.8.2 for Windows builds
* openssl 1.0.1c
Bug fixes -
* When running -testnet, use RPC port 18332 by default.
* Better detection and handling of corrupt wallet.dat and
blkindex.dat files. Previous versions would crash with a
DB_RUNRECOVERY exception, this version detects most problems and
tells you how to recover if it cannot recover itself.
* Fixed an uninitialized variable bug that could cause transactions
to be reported out of order.
* Fixed a bug that could cause occasional crashes on exit.
* Warn the user that they need to create fresh wallet backups after
Re: [Bitcoin-development] On bitcoin testing
thanks for the great reply jeff. i'm going to get a virtual machine set up on my system later tonight so at the very least, i myself can start testing. steve - haven't heard from you in almost a week. I'd still really like to get a look at the test cases and such you set up. Arklan -- As long as there is light, the darkness holds no fear. And yet, even in the deepest black, there is life. - Arklan Uth Oslin I want to leave this world the same way I came into it: backwards and on fire. - Arklan Uth Oslin On Tue, Oct 9, 2012 at 5:12 PM, Jeff Garzik jgar...@exmulti.com wrote: Copying from a response posted to Bitcoin software testing effort https://bitcointalk.org/index.php?topic=117487.0 as it is relevant to a recent thread here... Any level of testing is useful and appreciated. Various types of testing that are helpful: * it works testing: Simply run the latest Release Candidate (or latest version, if released). Make sure all the basics work (for whatever definition of basics you desire). This is the level most accessible to casual users. * Major features testing: Develop a short checklist of must-work features, and organize volunteers to work together and go through that checklist, item by item. Test each major feature on each major platform. * Stress and fuzz testing: Attempt to stress the system somehow, or randomly corrupt bits of data. See what breaks. * Regression testing: Record bugs fixed, and develop automated test cases that successfully reproduce the bugs on older versions, and verify newer versions remain fixed. * Unit function testing: Rigorously exercise each C++ class to ensure it behaves as expected at a micro level. * Full peer automated testing: Automated testing of RPC and P2P functions is non-existent, because of the difficulty in doing so. Find a solution to this problem. * Data-driven tests: If possible, write software-neutral, data-driven tests. This enables clients other than the reference one (Satoshi client) to be tested. Embed tests in testnet3 chain, if possible. The community at large can be a big help simply by doing the first item: download and run the Release Candidates and the latest version, and report any problems. Even reporting success is fine by me, for example: Version 0.7.1 works for me on Windows 7/32-bit posted on a forum thread. It is always very difficult to organize any sort of testing regime with open source volunteers that come and go. Each volunteer chooses their level of involvement. Any amount of testing and test-case writing, large or small, is helpful to bitcoin. -- Jeff Garzik exMULTI, Inc. jgar...@exmulti.com -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Bitcoin Testing Project
Hi guys. So, as I mentioned on the bitcointalk.org forums thread about the foundation, I want to get involved in the QA side of bitcoin development. I've done functional testing in the video game industry for years. I've read all the messages in this thread, but I'm left unclear how I can most effectively and quickly being helping out. Could I get a bit of a directional nudge? Arklan -- As long as there is light, the darkness holds no fear. And yet, even in the deepest black, there is life. - Arklan Uth Oslin I want to leave this world the same way I came into it: backwards and on fire. - Arklan Uth Oslin On Sat, Sep 29, 2012 at 12:26 PM, steve st...@mistfpga.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Gavin, Sorry for the delayed response, I wanted to take a couple of days to reflect on your email. On 26/09/2012 19:09, Gavin Andresen wrote: And their are other methods too. The GUI::Test package for perl will allow this to be greatly automated. (I have done this before on the localisation of photoshop.) this why we need detailed testscripts and plans. so we know what has and hasnt been done. The more boring the task the more work that needs to go into testcase development. This is the area I see as my greatest failing last time. I have a large number of virtual machines and should have at least this work. But we need very detailed testcases. with decent testplans just downloading the software, syncing the block chain, syncing an existing wallet, rescanning the blockchain and verifying the balance would cover a large number of tests. The idea behind having lots of very specific testcases is you get to see what tests have not been run. I understand your concern, however I have taken a couple of days to reflect on this and I still strongly feel that in order to make sure that this sticks, and is still useful in 1 years time we need to lay proper foundations. Those foundations are not word documents, spreadsheets, etc. they are selecting the right tools for the job. We can gain so much benefit from using 3rd party software. (bettermeans would rock if it wasnt rotting) I am sure you could do your coding work just using vi, but an sdk makes it much easier and allows you to work in a more productive manner. I have had a couple of off list emails with some testers and they also feel that it is very important to make sure we have a sound foundation (mantis is so much more than just a bug reporting tool, I see the bug reporting functionality as secondary to the main test run functionality - but it doesnt have to be mantis based, we do need workflow and testcase software though - and proper software for this is much better than just a massive google doc.) however I am checking out some other software that has been recommended. It will be very hard to change 'the process' once we have something we are used too (just look at the current resistance) I promise nothing will change for the dev team. But test does need other tools, and processes. If you feel that strongly that I am going about this the wrong way, I am happy to step back and let someone else sort it out (I will still do all the testing I possibly can). I would feel that this would be a real shame and we have the chance to setup requirements to functionality to tests all with traceability. why not do it right from the start? I will open up my vps' somepoint over the next few days and you can see what I mean. I will setup a fake git project, and sort out the interactions. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQEcBAEBAgAGBQJQZz1pAAoJEFvEB9dQFvtQRLkIAJtPCkW1R9vmMPY9u4o+ET1t w4pV/+W2PXo2p86HnljCIPLV/cua/1I/EJp7XR7s145Nj4KZUbzHGhvUUmwDOHW2 TGvJs+HO1bjsJfh4pWEb6PXcW3TguZxZSt5/rBAAI/5BeomSuRcZOdoV87D1xnK8 TSlgaseWrJcpKLO30/FQA3QnH/bjJ4OBmtHp8WaOtSnfww9Zbb5VYca37O15c2U4 2d0RUunDg1w2kRbkKjztxr3YasSOX+07Uvj4d5Lw7zgA0U93krNWVT1Ypo94dNJ7 6SyKi30UuqDdJ9XxZrMB/LBVNGOLlIBNWL++ocu5GFnOn9pnw57ZMBZM5g6YDpo= =ekQ/ -END PGP SIGNATURE- -- How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development -- Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com
