Published on: 2012-10-03T16:11:39+00:00
Steve, a Bitcoin developer, is looking to create a QA environment that will enhance testing and allow testers to excel. He believes that Git is too developer-centric for organizing testing, but acknowledges its compatibility with a large amount of software. The linking between bugs, requirements, fixes, re-tests, and regression test plans is deemed vital. Steve also mentions the need to organize testing campaigns, assign tests, work units, and relevant documentation/scripts/ideas.Currently, there are four potential places to report bugs - Jenkins (and unit tests), Git, the mailing list, and forums such as Bitcointalk. However, Github has become the authoritative place to report issues. Failed tests are reported on Github by the pull tester. There are currently 232 issues on Github, classified into categories like "Bug," "Improvement," "GUI," and "Wallet." Github issues can be easily referred to in commits using #123 with automatic linking. While other bug reporting systems may exist, Wladimir, another Bitcoin developer, does not see the value in switching to another system.In an email, Steve expresses his desire to shift away from Bettermeans and focus on test-driven development with a strong emphasis on requirements management and automation. He has been developing rudimentary requirement sets, basic requirement tracking, and stress tests to prove the requirements. Steve has installed open-source applications like Mantis, SalomeTMF, and Bugzilla to evaluate the best workflow process. He is finalizing workflow flow diagrams and welcomes anyone interested in helping or reviewing the processes to reach out via email.In September 2012, Wladimir and Daniel F discuss the addition of a developer resources page to bitcoin.org. Wladimir agrees to write the page, which would link to an editable and expandable wiki page for developer resources. They decide that adding a direct link to the developer resources page on the main site makes sense since the front page already has wiki links.On September 26th, 2012, Wladimir proposes creating a page on bitcoin.org that would link to a wiki page of developer resources. He acknowledges the potential for disagreement but suggests being pragmatic. This separate page would provide an easy link from the main site while still allowing for editable and expandable content.Bitcoin developer Matt Corallo discusses the usefulness of pulltester and Jenkins, stating that both run the same set of scripts. He suggests keeping them and improving if necessary. Corallo also proposes creating a page that links all the developer resources for Bitcoin development, including information on checking out the source code, contribution guidelines, where to ask development problems, and which bugs to solve first. While willing to write this page, he acknowledges that it may spark discussions about what should be included on bitcoin.org.In another email, Steve requests help with reviewing processes or even just encouragement. Another person responds, expressing limited availability but providing encouragement and emphasizing the importance of more testing. The email thread includes a promotional message for a Live Security Virtual Conference covering endpoint security, mobile security, and malware threats. It also mentions the Bitcoin-development mailing list.Overall, the discussion revolves around testing tools and methodologies in the context of Bitcoin development. Steve is seeking to create a conducive QA environment, while Wladimir and Daniel F discuss adding a developer resources page to bitcoin.org. Matt Corallo emphasizes the usefulness of pulltester and Jenkins and proposes linking all developer resources. The emails highlight the importance of testing and invite assistance and reviews from interested parties.
Updated on: 2023-08-01T03:56:40.402090+00:00