Cross-functional testing is verification of non-functional requirements.
These requirements are such characteristics of system that cannot be implemented like a normal feature.
Eg. Number of concurrent users supported by system, usability of site etc.
Cross-functional testing is related to cross-functional requirements.
Often business users do not specify cross-functional requirements in the beginning.
But they expect these when software is complete and deployed to production.
It is always a good idea to ask business users about such cross-functional expectations in initial phase of the project itself.
xxxxxxxxxx
import java.io.*;
import java.util.*;
import junit.framework.*;
public class PackageDependencyCycleTest extends TestCase {
private JDepend jdepend;
protected void setUp() throws IOException {
jdepend = new JDepend();
jdepend.addDirectory("/path/to/project/A/classes");
jdepend.addDirectory("/path/to/project/B/classes");
}
public void testAllPackages() {
Collection packages = jdepend.analyze();
assertEquals("Cycles exist",
false, jdepend.containsCycles());
}
}
https://learning.oreilly.com/library/view/full-stack-testing/9781098108120/ch10.html
xxxxxxxxxx
Cross-functional testing is a verification of non-functional requirements, i.e. those requirements which cannot be implemented like a normal feature.