WifiManagerTest was waiting for SUPPLICANT_STATE_CHANGED_ACTION
after enabling or disabling WiFi. Fix the code to check if the
WiFi state is already the desired state, and if not, to wait for
the WIFI_STATE_CHANGED_ACTION broadcast intent.
Bug: 7082455
Change-Id: Id1c2242c32311084f5587ea5403f6b227d1b8b04
Ensure the packet count test does not fail due to a single attempt.
Our goal is to just ensure the packet count API exists.
Bug: 7001746
Change-Id: I8c6604528946166969126cd5b085024f81790a77
The new WiFi watchdog requires kernel/driver to export some packet loss
counters. This CTS tests whether those counters are correctly exported.
Change-Id: Ic764eff64ff2ef354b46f17e46eb74b14f191e4c
wifiConfigurations returned by getConfiguredNetworks() can be null.
It is only incidental that this test passed fine in the past.
Bug: 6822950
Change-Id: I570ab6e7fd6cc5eb150914a5d7ca527ccc2f16cd
Poll a bit longer waiting for getNetworkId and getWifiState to return
the proper values. The bug reports seem to indicate that the WiFi
is shutting down properly.
Add a new static check method to PollingCheck that I think is simpler
than the existing way of creating a new PollingCheck, overriding
check, and then making sure to call run. This new variation also allows
you to specify a message rather than just "unexpected timeout."
Bug 6443337
Change-Id: I9f7c942f6e26b957bb717b58b1ab984acc556bf7
Check if type of network is supported on the devices.
The device supporting TYPE_WIFI returns failureCode(-1).
But, not supported device returns wifiOnlyStartFailureCode or
wifiOnlyStopFailureCode.
Change-Id: I070bb19f6740367c476e78b884c2a36d111ff3ee
Make sure to wait first and then check the expected state rather than
check the expected state first and then waiting.
Bug 6293413
Change-Id: Ibcb1127b935708c51fafdc8624cb3a7eefc01bda
com.android.cts.stub is growing very large. Split apart some of
the popular components into separate static libraries. This
should allow packages to depend on the components they need
rather than all of cts.stub.
Current code at the moment doesn't have to be changed, because
I have CtsTestStubs depending on these new shared libraries.
However, change the net package to depend on the ctstestserver
static library as a proof of concept rather than including
its source directly.
Change-Id: I32c54eab3ddfb1d4391d6ffc347fbc9cb2fe97f9
Explicitly include CtsTestServer in Android.mk to eliminate the
dependency to cts.stub. This allows net.cts to instrument itself,
and it also allows network-specific JNI code to be added in the
same package.
Change-Id: I624f87e0112619c5b97f2c3589933f666665fa8e
These annotations are not being parsed by any program.
Also they are distracting to readers and are painful to
maintain. Furthermore, they prevent us from adding the
LOCAL_SDK_CURRENT clause to Makefiles which is useful
to detect and stop us from using private APIs.
Change-Id: Id93b3a80c73df808c342e489f1434261f288204c
buildCts.py was the central script that generated all the
test package XMLs each time CTS was built. This had a
couple problems:
1. All the XML files for ~40 packages needed to be made
every time CTS was made. Even if those packages were
not touched at all.
2. Couldn't shard the XML generation process across the
available cores on a machine. A pool was added to the
python script, but it was set to a fixed number.
This change moves the test XML generation into a
smaller Java program called "cts-java-scanner" and
the doclet it relies upon to scan the Java files
into "cts-java-scanner-doclet.jar". The output of
the scanner like "cts-native-scanner" for native EXEs
is piped to the existing cts-xml-generator to
produce the test XMLs.
New CTS specific rules replace the standard
BUILD_PACKAGE and BUILD_HOST_JAVA_LIBRARY. They just
add extra rules for the package XML. The BUILD_CTS_PACKAGE
rule also adds a rule for copying the "package.apk"
to something more like "CtsFooTestCases.apk" to the
test case out directory. All the apks, exes, and xmls
are now thrown into a "cts-testcases" directory, before
they are copied to the final CTS distribution.
This change should prevent rebuilding the XMLs
unnecessarily and make rebuilding CTS quicker while
writing tests.
There are still the libcore tests that are always rebuilt,
but they can be adapted to fit into this model someday...
Change-Id: I52a916aa37fd679057e2709bb0ccec694c9fca01
* commit 'dc37b7251c8edd3e73797c4d0e3acb6df192fb59':
DO NOT MERGE Update CTS Version to 2.3_r10
Add SKT/KT rule into CtsTelephonyTestCases and use MCC+MNC code to distinguish SKT or KT carriers.
Fix AudioRecordTest to skip setUp() and tearDown() when MIC is not available.
fix IPv6 loopback pattern
Update the list UNSUPPORT_DATA_SMS_MESSAGES
Adjust the value of individualStartTimeoutMs to be consistent with the value of testStatusTimeoutMs.
Revert "Changed CTS runner to work with emulator"
Disable CTS Verifier BT Connection Access Tests
Fix Test Blacklist Mistake for HC MR2
Update CTS Verifier Version to 3.1 R2
Update CTS Version to 3.1 R5
Move the ListeningPortsTest from android.net.cts to android.security.cts,
to better indicate that this is a security related test.
Start triggering test failures when a process is bound to the loopback
interface. In those cases, it's always better to use a UNIX domain
socket instead of a locally bound IP socket. UNIX domain sockets
can be protected with unix filesystem permissions, or
getsockopt(SO_PEERCRED) can be used to indicate who is on the
other end of the socket.
Drastically fix the documentation to explain why this test is present.
Modify the IP addresses and port numbers to be more human readable.
Change-Id: Id83aadd1455279a1a2d3fb4fb1915af558355aca
* commit 'cb8b1d9566e122812b7da9346254bb97eb06bc40':
Only install necessary prequisite apks.
Execute remaining tests in order.
fix IPv6 loopback pattern
DO NOT MERGE Adjust test start date
Retain META-INF in core-tests.
Fix a mismatch problem because of hidden public API in CamcorderProfile.java
Update CTS Verifier Feature Summary
In /proc/net/udp6 and /proc/net/tcp6, the addresses stored
in that file are in network byte order. As a result, the IPv6
loopback address, ::1, is stored as
00000000000000000000000001000000 NOT
00000000000000000000000000000001
Bug: 5473686
Change-Id: I73098d52c981c48d82423c8ce99b6b20d11a5568
In /proc/net/udp6 and /proc/net/tcp6, the addresses stored
in that file are in network byte order. As a result, the IPv6
loopback address, ::1, is stored as
00000000000000000000000001000000 NOT
00000000000000000000000000000001
Bug: 5473686
Change-Id: I73098d52c981c48d82423c8ce99b6b20d11a5568
