PC² is the Programming Contest Control System developed at California State University, Sacramento in support of Computer Programming Contest activities of the ACM , and in particular the ACM International Collegiate Programming Contest . It was used to conduct the ACM ICPC World Finals in 1990 and from 1994 through 2009. In 2010, the ACM ICPC World Finals switched to using Kattis, the KTH automated teaching tool; however, PC continues to be used for a large number of ICPC Regional Contests around the world.
18-416: Computer programming contest have rules and methods for judging submissions. The following describes in a general way a contest where PC is used. A computer programming contest is a competition where teams submit (computer program) solutions to judges. The teams are given a set of problems to solve in a limited amount of time (for example 8-13 problems in 5 hours). The judges then give pass/fail judgements to
36-438: A previous result that is known to be good, without any knowledge of the test object's internal structure. Typical black-box test design techniques include decision table testing, all-pairs testing , equivalence partitioning , boundary value analysis , cause–effect graph , error guessing , state transition testing, use case testing, user story testing, domain analysis , and syntax testing. Test coverage refers to
54-428: A way to request team solutions (from a PC server) run/execute the solution and enter a judgment. The PC scoreboard module computes and creates standings and statistics web pages ( HTML / XML ). PC is easy to install on Linux /Linux-like systems and MS Windows and does not require super-user (root) access to install it or use it: this makes it an attractive choice for users who may not have super-user access. PC
72-442: Is a method of software testing that examines the functionality of an application without peering into its internal structures or workings. This method of test can be applied virtually to every level of software testing: unit , integration , system and acceptance . Black-box testing is also used as a method in penetration testing , where an ethical hacker simulates an external hacking or cyber warfare attack with no knowledge of
90-554: The PC development team has quickly responded to questions and help with any issues that came up. PC has been in use by the ACM Mid-Atlantic Programming Contest for several years. In earlier years, systems administrators had limited success with the program due to its distributed nature. Each of the contest sites ran a PC server which needed to initiate and accept Java RMI . Using a central datacenter in
108-748: The Regional Contests are fed by sub-regional contests, all of which also use PC . The winners at each Regional Contest advance to the ACPC Championship, which also uses PC . ACPC also sponsors a variety of additional contests, including "ACPC Kickoff", "ACPC for Girls", "ACPC for Teens", and "ACPC for Seniors"; again, all of these contests also use PC . The ICPC (formerly ACM) Greater New York Regional Programming Contest in North America has been using PC for over 20 years. Greater New York has used PC many different ways over
126-658: The U.S. It remains today the single most widely used Contest Control System for ICPC Regional Contests. PC has been used by the Africa and Arabia Collegiate Programming Contest (ACPC) every year since its inception more than 25 years ago. ACPC comprises a set of Regional Contests, including the separate Saudi, Nigerian, Oman, South Africa, Togolese, Moroccan, Kuwait, Algerian, Jordanian, Palestinian, Qatar, Beninese, Egyptian, Lebanese, Ethiopian, Tunisian, Bahrain, Sudanese, Syrian, and Angolan Collegiate Programming Contests. Every one of these Regional/National Contests uses PC ; many of
144-409: The application is supposed to do. Test cases are generally derived from external descriptions of the software, including specifications, requirements and design parameters. Although the tests used are primarily functional in nature, non-functional tests may also be used. The test designer selects both valid and invalid inputs and determines the correct output, often with the help of a test oracle or
162-449: The application's code, internal structure and programming knowledge in general is not required. The tester is aware of what the software is supposed to do but is not aware of how it does it. For instance, the tester is aware that a particular input returns a certain, invariable output but is not aware of how the software produces the output in the first place. Test cases are built around specifications and requirements , i.e., what
180-508: The contest. Because of these incidents, organizers of the region are now considering moving to an alternative system, such as Kattis, which is the official system used by ACM for the ICPC World Finals. With the introduction of version 9 ( socket -based version) delays, most firewall issues with version 8 have been addressed. Black box testing Black-box testing, sometimes referred to as specification-based testing ,
198-449: The fall of 2005 revealed no problems. In 2014, PC crashed 3:45h into the contest, preventing teams from obtaining receipts for their submissions. Judges were unable to retrieve submissions - the contest ended without announcing a winner. It took one week to try to recover those submissions. A similar failure occurred in 2016. System administrators had decided to deploy a web add-on to PC which then failed under load. The contest start time
SECTION 10
#1732780823031216-454: The given requirements. Black-box testing may be necessary to assure correct functionality, but it is insufficient to guard against complex or high-risk situations. An advantage of the black box technique is that no programming knowledge is required. Whatever biases the programmers may have had, the tester likely has a different set and may emphasize different areas of functionality. On the other hand, black-box testing has been said to be "like
234-476: The percentage of software requirements that are tested by black-box testing for a system or application. This is in contrast with code coverage , which examines the inner workings of a program and measures the degree to which the source code of a program is executed when a test suite is run. Measuring test coverage makes it possible to quickly detect and eliminate defects, to create a more comprehensive test suite . and to remove tests that are not relevant for
252-446: The submitted solutions. Team rankings are computed based on the solutions, when the solutions were submitted and how many attempts were made to solve the problem. The judges test in a Black box testing where the teams do not have access to the judges' test data. PC manages single or multi-site programming contests. It provides a team a way to log in, test solutions, submit solutions and view judgements from judges. PC provides judges
270-423: The system being attacked. Specification-based testing aims to test the functionality of software according to the applicable requirements. This level of testing usually requires thorough test cases to be provided to the tester, who then can simply verify that for a given input, the output value (or behavior), either "is" or "is not" the same as the expected value specified in the test case. Specific knowledge of
288-545: The years including single site, multi-site and the Web-based team client. The judges in the Greater New York region prefer PC over other Contest Control Systems since it gives them the greatest flexibility in judging contestant submissions. Submissions may be judged manually or using computer auto-judging. Often, the judges prefer to judge some problems manually, and PC provides this capability. In addition,
306-407: Was delayed by 90 minutes. Teams were unable to submit problems and the contest director scrambled to find a work-around that let teams save problems with a time stamp to be considered later. In 2013, system operators failed to enter the correct team names, leaving teams without information about the standings in the contest (the scoreboard). System operators were unable to correct the team names during
324-707: Was used for the ACM International Collegiate Programming Contest World Finals from 1994 to 2009. It has also been used in hundreds of ICPC Regional Contests around the world. It has been used continuously by the ACM Pacific Northwest Regional Contest since 1989, as well as by many other ICPC Regional Contests including the Africa and Arabia Regional Contests, numerous Regional Contests in Asia, and several Regional Contests in
#30969